E.15. Postgres Pro Standard 13.9.1
Release Date: 2022-11-24
E.15.1. Overview
This release is based onPostgreSQL 13.9 andPostgres Pro Standard 13.8.2. All improvements inherited fromPostgreSQL 13.9 are listed inPostgreSQL 13.0 Release Notes. Other major changes and enhancements are as follows:
Added support for Ubuntu 22.10.
Added support for Elbrus CPU architecture through ALT 9/10 for e2kv3/e2kv4, ALT 8.2 SP for e2kv3/e2kv4 and Astra Linux Leningrad 8.1 operating systems. You are recommended to use the 5.4.182-mcst-e8c-alt3.22.1 Linux kernel or newer when running ALT 10 for e2kv3/e2kv4.
Fixed huge selectivity overestimation observed in rare cases, which could result in a sequential scan of a whole relation instead of a quick index scan, so certain queries were executed much more slowly than expected. The issue was due to an oversight in a recent optimization of selectivity estimation.
Fixed bursts in the
checkpoint_reqcounter of thepg_stat_bgwriterview on a replica that occurred from time to time due to a series of unsuccessful attempts to create a restartpoint. The fix checks in advance whether an attempt to create a restartpoint will fail and thus prevents from making obviously unsuccessful attempts. Note that the issue did not cause excessive consumption of system resources even before it was fixed.Addedrum module, which provides RUM index based on GIN, to Postgres Pro Standard.
Addedpg_wait_sampling extension for sampling-based statistics of wait events to Postgres Pro Standard. With this extension, you can get an insight into the server activity, including the current wait events for all processes and background workers.
Added theoracle_fdw extension to Windows versions of Postgres Pro.
Upgradedaqo to version 1.5, which contains bugfixes and the following changes:
Switched to storing the knowledge base on disk outside of the database. Previously it was stored inPostgres Pro tables.
Madeaqo relocatable.
Added functions to analyze the quality of query planning.
Added a possibility to learn from partially completed queries, namely, from those that timed out (seestatement_timeout).
Madeaqo use the same query ID as other extensions. Soaqo andpg_stat_statements can be used simultaneously, sharing the same query IDs.
Enabledaqo work with temporary tables.
Fixed a few memory leaks.
Added alpha version of a new feature: search by neighbors (off by default). It allows applying knowledge to newly added queries with a different structure.
Upgradedmamonsu to version 3.5.2, which provides new features and bugfixes. Notable changes are as follows:
Added autovacuum utilization metrics.
AddedZabbix macros based on plugin parameters from the configuration file, so that triggers can now be dynamically changed directly inZabbix without updating the configuration file and restartingmamonsu.
Upgradedpg_probackup to version 2.5.10, which provides optimizations and bugfixes. Notable changes are as follows:
Fixed an issue with
checkdb--amcheck, which previously completed with an error when the checked database contained partitioned indexes.Fixed a backup failure on a replica that occurred because the version of thepg_probackup agent running there was different from that on the primary.
Upgradedpgpro_pwr to version 4.1, which mainly adds JIT-related statistics to report tables.
Upgradedpgpro_stats to version 1.4.3, which provides bugfixes. In particular:
Fixed possible server crashes that could occur during query text normalization when an extended protocol was used.
E.15.2. Migration to Version 13.9.1
If you are upgrading fromPostgres Pro Standard based on the samePostgreSQL major version, it is enough to install the new version into your current installation directory.
When upgrading fromPostgres Pro versions 13.2.1 or lower, rebuild indexes containing at least one included column of type for which the collation was defined in the table.
If you are upgrading fromPostgres Pro versions 13.2.2 or lower and takePTRACK backups usingpg_probackup, retake a full backup after upgrade.
To migrate fromPostgreSQL or aPostgres Pro Standard release based on a previousPostgreSQL major version, see the instructions inPostgres Pro Standard 13.1.1 Release Notes.