E.12. Postgres Pro Standard 12.13.1
Release Date: 2022-11-23
E.12.1. Overview
This release is based onPostgreSQL 12.13 andPostgres Pro Standard 12.12.2. All improvements inherited fromPostgreSQL 12.13 are listed inPostgreSQL 12.13 Release Notes. Other major changes and enhancements are as follows:
Added support for Ubuntu 22.10.
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.
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.
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 master.
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.12.2. Migration to Version 12.13.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.
While functionsnumeric_eq,numeric_ne,numeric_gt,numeric_ge,numeric_lt, andnumeric_le are actually leakproof, they were not marked as such inPostgres Pro Standard 12.1.1, which could lead to incorrect query optimization. In particular, it negatively affected query execution if row-level security policy was in use. Version 12.2.1 repairs this issue for new installations by correcting the initial catalog data, but existing installations will still have incorrect markings unless you updatepg_proc entries for these functions. You can runpg_upgrade to upgrade your server instance to a version containing the corrected initial data, or manually correct these entries in each database of the installation using theALTER FUNCTION command. For example:
ALTER FUNCTION pg_catalog.numeric_eq LEAKPROOF
When upgrading fromPostgres Pro versions 12.6.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 12.6.2 or lower and takePTRACK backups usingpg_probackup, retake a full backup after upgrade.