PGConf.Russia 2025

The work of a DBA is very multifaceted: backups, version updates, performance issues — there's a long list. But sometimes, due to the workload, we don't give enough attention to innovations that don't directly relate to what we do every day. Such is the case with logical replication.

Of course, each of us has some skills working with this tool, but PostgreSQL is a rapidly evolving database system. Sometimes, we simply need to look around with a fresh perspective to see something new.

My presentation will be based on this approach: we'll start with theory (as always, less theory, more practice) and simple examples, then move on to more complex examples of its use. Special attention will be given to what has changed in modern versions of PostgreSQL.

This presentation will be helpful for those who want to get acquainted with logical replication or refresh their knowledge of this tool.

A brief presentation on various extensions that can assist with optimization.

Although we often don't like to talk about it, database administration carries with it a large amount of stress. This is particularly true when we have to take on late night support duties. In this talk you will learn: 1. The basics of the physiology of stress. This is not a physiology lecture, but as engineers we need enough to build a mental model. 2. What kinds of mistakes we make when under stress. 3. How to measure stress in your own life and recognize it in others. 4. What tools are helpful to manage short- and long-term stressors. Managing short-term stress is important in avoiding becoming overwhelmed when problems occur, but managing longer-term stressors is just as important in avoiding problems in the first place.

Not a PgBouncer, But a Connection Pooler. Not Odyssey, But with Coroutines

If you’ve ever set up a high-availability PostgreSQL cluster, you’ve likely faced the challenge of redirecting traffic to the primary node after a failover.

Typically, this requires additional software to monitor cluster status and reroute traffic accordingly. To avoid a single point of failure, you may have had to implement failover handling within that layer. Additionally, you might have encountered PostgreSQL’s limitations on handling large numbers of concurrent client sessions, necessitating query pooling.

To solve these issues, we developed Proxima — a scalable, fault-tolerant proxy and connection pooler. Proxima automatically redirects traffic to the primary node and, in BiHA setups, seamlessly switches to a new primary in case of failure.

In this talk, I’ll cover why and how we built Proxima, the key architectural decisions behind the extension, and the

implementation details that enable it to handle 10,000+ concurrent client sessions.

We’ll also explore use cases and answer your questions.