PGConf.Russia 2025

In PostgreSQL performance testing, benchmarks measure query execution time (latency). To get more reliable results, queries are executed repeatedly, generating a dataset of latency values. Performance is often assessed using standard metrics like the median or mean, but we propose a more advanced approach.

In practice, latency distributions are often multimodal, consisting of multiple underlying distributions with distinct characteristics. In such cases, traditional statistical methods are insufficient, requiring a more detailed analysis of the dataset’s structure.

Our work presents a tool that automatically performs statistical analysis of benchmark results, accounting for dataset-specific features. It detects multimodality, identifies the number and boundaries of dominant modes, and determines key distribution parameters—providing deeper insights into PostgreSQL performance variations.

For DBAs, ensuring database protection and integrity is always a top priority. Along with that comes the need to store data efficiently and compactly, without overloading the network, and ensuring reliable recovery.

In this talk, we’ll discuss a universal solution for backup and archive storage that not only offers effective deduplication but also minimizes network load. TATLIN.BACKUP is a platform for storing PostgreSQL backups or WAL archives with compression, deduplication, and minimal data transmission over the network.

TATLIN.BACKUP is a versatile solution for transferring and storing PostgreSQL archives at remote locations from a central office.

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.

Diagnostic Methods: Analyzing the Issue of Long CREATE DATABASE Execution

This talk covers two cases of long CREATE DATABASE execution in PostgreSQL 11, which, in a Corosync/Pacemaker cluster configuration, caused node failover due to a monitoring timeout from the clustering software. The first case is related to a large shared buffers size, while the second involves the use of the WITH OWNER option during database creation and a large pg_shdepend system table (a feature of using the jBPM software).