PGConf.Russia 2025

Where I used to work, we had pushed ElasticSearch to its breaking point. We needed an even more scalable replacement for a write-heavy, read-seldom workload. So we built one on PostgreSQL. Now, many of us are building the successor as an open source project. 

This talk goes over the design of Bagger (named after the giant mining machines), which can manage logs into tens or hundreds of petabytes. More than just a review of the architecture, this talk focuses on the whys and the tradeoffs made in the design. 

The talk is intended both to showcase how programmable and powerful PostgreSQL is, but also illustrate the fundamental tradeoffs which must be faced when pushing any technology into the big data space.

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.

In 2024, Postgres Professional introduced pgpro-otel-collector, a new tool for gathering PostgreSQL telemetry data using OpenTelemetry technologies and standards.

In this talk, I’ll explain why we chose OpenTelemetry, showcase the features of pgpro-otel-collector, and demonstrate how it helps streamline telemetry collection within a monitoring infrastructure.

This talk explores the challenges we encountered — and solved — while migrating massive databases from Oracle to PostgreSQL.

One of the most complex aspects of this process was rebuilding foreign keys (FKs). To overcome these challenges, we had to dive deep into the internal workings of FK creation and validation.

Key topics include:

Does ALTER TABLE ... ADD CONSTRAINT ... FOREIGN KEY have an execution plan?

Can an ordinary user influence this process?

What locks are applied during FK creation and validation?

Also, we’ll introduce a first-principles method for investigating performance issues, applying it to a real-world FK creation bottleneck.