E.11. Postgres Pro Standard 11.15.1
Release Date: 2022-02-22
E.11.1. Overview
This release is based onPostgreSQL 11.15 andPostgres Pro Standard 11.14.1. All improvements inherited fromPostgreSQL 11.15 are listed inPostgreSQL 11.15 Release Notes. Other major changes and enhancements are as follows:
Increased the number of partitions of the shared buffer mapping hash table to 1024, which can improve performance on multi-core systems.
Fixed the use of multi-column statistics by planner. Previously, when the optimizer estimated the query selectivity using multi-column statistics and the query conditions only included part of the columns involved, the cardinality could be considerably overestimated, so the created plan would be non-optimal.
Fixed the out-of-memory (OOM) killer settings in system startup files. Previously the OOM score adjustment value was set for all Postgres Pro processes rather than forpostmaster only, so when Postgres Pro exhausted all RAM, the OOM killer could start killing irrelevant processes, such assshd.
Ended support for outdated operating systems Debian 8, Astra Linux Smolensk 1.5 and MSVSphere 6.3.
Upgradedpg_probackup to version 2.5.5, which provides the following new features and bugfixes as compared to the previous included version 2.5.3:
Added the
--checkuniqueoption to thecheckdbcommand to work together with--amcheckand verify unique constraints during logical verification of indexes when theamcheck extension is installed in the database and its version supports the verification of unique constraints. Check theamcheck documentation for whether this verification is supported.Fixed an issue that could occur when the source database was not on the timeline 1 and the destination database did not fall behind:probackup sanity checks on
catchuptimeline history failed with the error“Destination is not in source timeline history”.Fixed the behavior of
catchupinDELTAandPTRACKmodes. The fixed issue could occur whenpg_probackup operated remotely via SSH and--destination-pgdatawas the same as--source-pgdata, caused corruption of the source instance (at least theglobal/pg_control,global/pg_filenode.mapandbase/*/pg_filenode.mapfiles got deleted) and resulted in the error“Could not open file "/pgwal/test/global/pg_control" for reading: No such file or directory”.
E.11.2. Migration to Version 11.15.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.