PGConf.SPB 2023

We will present adaptive query optimization techniques and key capabilities of the new version of AQO and SR_PLAN extensions.

Traditionally, fault tolerance in Postgres is implemented using built-in replication mechanisms and external utilities that monitor the state of running Postgres instances and react accordingly when various failures occur. In this presentation, I will tell you what we like and what we don’t like about this approach, which alternative we see, what we have been able to achieve to date and what we want to get done by the time of release, which is planned for December.

Postgres Pro Enterprise is based on open source PostgreSQL. However, the difference is significant: the current version of Postgres Pro Enterprise has 40 more features that are not a part of PostgreSQL. 20 more mechanisms are being developed either as built-in features or separate products. This includes BiHA, DBaaS, pg_probackup, etc. In this presentation, we'll briefly discuss some of them.

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.