E.6. Postgres Pro Standard 11.18.1
Release Date: 2022-11-23
E.6.1. Overview
This release is based onPostgreSQL 11.18 andPostgres Pro Standard 11.17.2. All improvements inherited fromPostgreSQL 11.18 are listed inPostgreSQL 11.18 Release Notes. Other major changes and enhancements are as follows:
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.
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.
E.6.2. Migration to Version 11.18.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 11.6.1 or lower, which could lead to incorrect query optimization. In particular, it negatively affected query execution if row-level security policy was in use. Version 11.7.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
Version 11.7.1 also fixesSIMILAR TO and POSIX regular expressions that use character classes for icu collations, so you may need to check for objects that use such regular expressions.
Starting fromPostgres Pro Standard 11.6.1, the ICU library upgrade does not interfere with the server start. Before connecting to a database using ICU as the default collation,Postgres Pro compares this collation version to the one provided by the ICU library and displays a warning if the collation versions do not match; you may need to rebuild the objects that depend on the default collation if you think the collation change may affect the sort order of your data. To suppress these warnings, you can use theALTER COLLATION "default" REFRESH VERSION command, as explained inALTER COLLATION.
Sincepg_probackup delivery model changed inPostgres Pro Standard 11.2.1, when upgrading from a lower version on ALT Linux and Debian-based systems, runapt dist-upgrade (orapt-get dist-upgrade) to ensure that all new dependencies are handled correctly. On Windows, you have to run a separatepg_probackup installer to complete the upgrade.
When upgrading fromPostgres Pro versions 11.11.1 or lower, rebuild covering 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 11.11.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 themigration instructions for version 11. If you are opting for a dump/restore, make sure to use the--add-collprovider option to correctly choose the provider for the default collation of the migrated database.