PGConf.Russia 2025

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.

Making changes to tables under production load is always a complex task. For example, when you need to change a column type (e.g., from int to bigint or from timestamp to timestamptz), or move a table to a different tablespace without losing any changes that occur during the data migration.

What if you have hundreds of such tables? With pg-transparent-alter-table, this is no longer a problem. These tasks can be solved with a single simple command:
$ pg_tat -h 0.0.0.0 -d mydb -c "alter table mytable alter column id bigint"

Key features include:

• You can specify any number of alter table commands at once.
• You can modify partitioned tables, supporting both the old inheritance-based partitioning and new declarative partitioning, including multi-level partitioning.
• You can interrupt the process at any stage and continue later without losing progress from previous stages.
• You can change your mind at any time, stop the execution, run "pg_tat --clean," and revert to the original state.
• Custom commands for changing column order.
• PostgreSQL version support: 11-17.

After more than 5 years of existence (previously called transparent-alter-type), the project has become a reliable tool actively used in production. I would like to share my experience and discuss its capabilities.

The visibility map in PostgreSQL is an important mechanism for optimizing database performance, accelerating read operations, data cleanup, and indexing. Despite some limitations, such as memory consumption and fragmentation, its use can significantly enhance performance in high-load systems. Effective utilization of the visibility map requires proper configuration and monitoring, which is especially crucial in systems with large data volumes and high transaction concurrency.

Databases are a core component of any information system, and query performance directly impacts overall efficiency.

Last year, we explored suboptimal queries and optimization techniques, and the topic proved highly relevant. In this second installment, we’ll cover:

Using extended statistics for computed columns

Pagination techniques for improved query handling

Real-world optimization examples from 1C