PGConf.Russia 2025

In some cases, business logic is implemented directly within the database. It's well known that maintaining and developing business logic becomes much easier when it's covered by tests. However, backend tests often treat the database as an external resource and don’t always interact with a live database.

This talk will introduce an enhanced version of the pgTap library, designed not only to facilitate unit testing and CI for database code but also to accelerate the development process itself.

I’ll talk about the challenges you’ll face if you decide to implement a new TableAM. What to choose: Generic XLog or Custom RMGR? Why use a Custom SMGR? How to integrate PostgreSQL allocators into third-party libraries, even if they don't officially support it? What’s missing for a columnar engine (including vectorization and late materialization), and how can we work around those limitations?

In the second part, I’ll dive into the internals of pgpro_tam — a new native table engine for OLAP that supports standard data formats, various SMGRs, and, if needed, third-party schedulers and execution engines, all while adhering to ACID principles. This is designed to achieve the fastest analytics on PostgreSQL (not just plugging in DuckDB).

Poolers play a crucial role in PostgreSQL database operations. In this talk, we’ll discuss the challenges we faced when using and implementing existing poolers and the benefits we gained by developing our own pooler.

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).