PGConf.Russia 2025

There are many administrator consoles out there, ranging from the old-school DBeaver to the ubiquitous pgAdmin. However, we decided to create another one. Why?

In this talk, you’ll learn:

• How can a single installation manage tens of thousands of database instances.

• How many users can the console support.

• How can you inventory your infrastructure without losing your sanity.

• How do you integrate into an existing environment without starting from scratch.

• How to build a security model that earns the trust of leading banks and telecom operators.

• How can you get hands-on experience with all of this.

Sometimes, issues arise with the operation of PostgreSQL on Linux. We will define a classification of these scenarios and provide solutions, from simple to complex. Which failures lead to data corruption? Which scenarios are more dangerous than others, and what should be monitored? We will review logging examples from DBM.P Skala-R and analyze debugging scenarios, including OS libraries, Linux kernel, drivers, and kernel modules to identify causes and resolve errors.

The issue of slow month-end closing and cost calculation on PostgreSQL has been a long-standing problem. In this talk, we will explore what modern versions of PostgreSQL offer in this regard and answer the question, "Do replicas slow down the master?"

We will also take a look at different types of physical replication and, for dessert, share a recipe for quick and painless month-end closing in 1C without affecting the daily operations of users.

The execution time of SQL queries depends on factors like indexes and up-to-date statistics. In most cases, optimizing slow queries helps resolve database performance issues.

But what if classic query optimization doesn’t work? What if the system keeps behaving unpredictably — or worse, crashes, leading to frustration, panic, and even despair?

In this talk, we’ll explore how Postgres Professional’s performance engineers tackle these challenges, look at the tools they use, what’s still missing, and where PostgreSQL performance optimization is headed