PGConf.Russia 2025

Greenmask is an open-source utility for database anonymization and synthetic data generation. A common challenge in development is creating test environments that closely resemble production. In this talk, we will explore how to use Greenmask’s features to prepare a test environment with ease. 

We will discuss its architecture, database subsets, types of transformations, the reasons for integrating with the PostgreSQL driver, and porting some pg libraries. Additionally, we will explain how our technology helps businesses solve problems faster, more efficiently, and securely.

Every day, thousands of engineers work tirelessly to make data more accurate, reliable, and up-to-date. But sometimes, we need to do the exact opposite—corrupt it.

Whether it’s masking or replacing sensitive information, or even generating entirely new datasets while preserving key business properties, data obfuscation is a crucial task. It’s essential for testing systems, sharing data with third parties, and more. However, given the complexity of data schemas and business logic, this is far from trivial.

In this talk, we’ll explore the challenges of working with artificial data and discuss various approaches to solving them using PostgreSQL’s built-in features and external extensions.

The execution time of SQL queries depends on factors like indexes and up-to-date statistics. In most cases, optimizing slow queries helps resolve database performance issues.

But what if classic query optimization doesn’t work? What if the system keeps behaving unpredictably — or worse, crashes, leading to frustration, panic, and even despair?

In this talk, we’ll explore how Postgres Professional’s performance engineers tackle these challenges, look at the tools they use, what’s still missing, and where PostgreSQL performance optimization is headed

As part of the import substitution process, we encountered the need to find a reliable alternative to Oracle. PostgreSQL was considered the primary candidate for replacement, but during the research, the "vanilla" version revealed a number of critical limitations that hindered a successful transition.

These issues included support for autonomous transactions, batch variables, and several other specifics. What is special about pg_settings? Why do we need autonomous transactions, and how do HOLD cursors relate to this? These and other topics will be discussed in our presentation, where we will also share our experience of implementing Postgres Pro Enterprise.