E.21. Postgres Pro Standard 14.2.1
Release Date: 2022-02-28
E.21.1. Overview
This release is based onPostgreSQL 14.2 andPostgres Pro Standard 14.1.1. All improvements inherited fromPostgreSQL 14.2 are listed inPostgreSQL 14.2 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.
Implemented support of
intervalvalues by all time parameters (*_TIME) ofCREATE PROFILEandALTER PROFILESQL commands.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.
Added support for Rocky Linux 8.
Ended support for outdated operating systems Debian 8, Astra Linux Smolensk 1.5 and MSVSphere 6.3.
Fixed an issue inpsql, which mistakenly treated the
\du+meta-command as invalid.\du+lists database roles showing additional information about each role and is equivalent to the\dg+meta-command, which was processed correctly.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.21.2. Migration to Version 14.2.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.
To migrate fromPostgreSQL or aPostgres Pro Standard release based on a previousPostgreSQL major version, see the instructions inPostgres Pro Standard 14.1.1 Release Notes.