PGConf.SPB 2023

During the years of its existence, Postgres Pro piled up a pool of problems when query execution was inappropriately slow or a query was too expensive to be executed, so it was never executed. Almost always in our practice, this was due to the choice of a non-optimal query plan. In our story, we will talk about a very unconventional attempt to solve this problem by re-planning queries. We will tell you what it is, how it works, who will find it helpful and the prospects for using this feature.

Postgres Pro is investing heavily to make it easy for customers to migrate to their database from Oracle Database.

This talk describes in detail the advanced Postgres Pro DBMS technologies designed to solve this problem:

• support for package functionality in PL/pgSQL, including the package initialization section and global package variables;
• ora2pgrpo utility for automatic conversion of package code from Oracle PL/SQL syntax to PL/pgSQL;
• PG Pro Application Info extension designed for instrumentation and monitoring of the state of sessions, including the execution of long operations (session longops) - a functional analogue of the package DBMS_APPLICATION_INFO in Oracle DBMS;
• new system packages UTL_MAIL and UTL_SMTP for sending emails from stored procedures to Postgres Pro DBMS (full functional analogue of the corresponding packages in Oracle DBMS);
• new system package UTL_HTTP for interacting with external sources from stored procedures in Postgres Pro DBMS (analogous to the package of the same name in Oracle DBMS);

Also in this talk there will be a short story about the directions of development of the Postgres Pro DBMS aimed at further simplifying migration from Oracle DBMS.

We will answer the questions about the importance of compression in backup process. Will show a demo how to use the following available algorithms: pglz, zlib, zstd, lz4 in different editions of pg_probackup. We'll show you how to make incremental backups and restore even faster with PTRACK and CFS (tablespace compression) in Postgres Pro. The plans for further development will also be announced.

One of the requirements for the operation of the Corosync/Pacemaker failover cluster is the fencing of the failed node. In virtual environments, fencing is implemented by disabling the virtual machine through a hypervisor, in a cluster on physical servers - through IPMI/ILO. But what if it is impossible to organize fencing, for example, in the cloud environment? During this presentation, I will list and explain alternative methods of fencing a failed node.