PGConf.Russia 2025

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.

Dozens of PostgreSQL instances have replaced a single large Oracle database. One of our key business systems was completely redesigned and rebuilt on an import-independent solution.  

This talk will cover the unique challenges, architecture, issues, and operational aspects of this migration. Expect an insightful deep dive into the process!

So much has been said about PostgreSQL as the result of its program code. But Postgres is not just code. It’s the people who create it, develop it, and... leave a piece of themselves through comments.

What stories can we uncover from the comments in PostgreSQL’s code? We’ll discover what the most popular word is, which comments have been in the code since the very first public commit, how the style of communication has evolved with the product, and how we can see the human side behind the lines of code and comments.

Experience Report addressing the manual migration of MS SQL Server Stored Procedures and Table-Valued Functions to PL/pgSQL. We chose a manual migration from T-SQL over using a PostgreSQL Extension with an automated translation. The motivation was that the T-SQL code contains non-trivial business logic for which we wanted idiomatic PL/pgSQL code. 

The T-SQL Code used features like 

• Mix of Stored Procedures and Table-valued Functions

• Table variables, (user-defined) table types 

• Recursive Common Table Expressions 

• Optional parameters 

The migration required

• Adopting naming conventions 

• Renaming parameters and local variables 

• Maping table types 

• Mapping table-valued parameters to arrays 

• Mapping table-valued return types to SETOF record

• Translating between arrays and tables 

In this session we will migrate a chain of dependend functions T-SQL functions to PL/pgSQL. We will work around quirks in both T-SQL functions and PL/pgSQL.