E.12. Postgres Pro Enterprise 11.15.1
Release date: 2022-03-09
E.12.1. Overview
This release is based on PostgreSQL 11.15 and Postgres Pro Enterprise 11.14.1. All changes inherited from PostgreSQL 11.15 are listed in PostgreSQL 11.15 Release Notes. As compared with Postgres Pro Enterprise 11.14.1, this version also provides the following changes:
Increased the number of partitions of the shared buffer mapping hash table to 1024, which can improve performance on multi-core systems.
Fixed an issue with lazy conversion from 32-bit to 64-bit transaction IDs in read-only transactions or on replicas by enforcing marking pages as subject to full-page writes to WAL. This issue could cause failures to synchronize conversion results to other replicas.
Fixed an issue with
*.cfmfiles that were unexpectedly left in compressed tablespaces after dropping a table.Fixed segmentation fault, which might have occurred when executing a specific procedure calling pattern while plan_cache_lru_size was set.
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 for postmaster only, so when Postgres Pro exhausted all RAM, the OOM killer could start killing irrelevant processes, such as sshd.
Ended support for outdated operating systems Debian 8 and Astra Linux Smolensk 1.5.
Upgraded mamonsu to version 3.4.0. Notable changes are as follows:
Added a new
timeoutparameter to the[zabbix]section of the mamonsu configuration file. It allows you to set maximum time to wait while connecting to the Zabbix server.Added a new
mamonsu dashboard uploadcommand, which can be used to upload a Zabbix dashboard with the mamonsu metrics to a template on the Zabbix server version 6.0 or higher.template_name
Upgraded pg_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 the amcheck extension is installed in the database and its version supports the verification of unique constraints. Check the amcheck 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 when pg_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.12.2. Migration to Version 11.15.1
If you are upgrading from a Postgres Pro Enterprise release based on the same PostgreSQL major version, it is enough to install the new version into your current installation directory.
Migration of a cluster with tables larger than 16Tb to Postgres Pro Enterprise versions 11 or 10 is not supported.
If you have previously migrated to Postgres Pro Enterprise 11.12.1 or lower, you must run the REINDEX command to rebuild GIN indexes.
While functions numeric_eq, numeric_ne, numeric_gt, numeric_ge, numeric_lt, and numeric_le are actually leakproof, they were not marked as such in Postgres Pro Enterprise 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 update pg_proc entries for these functions. You can run pg_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 the ALTER FUNCTION command. For example:
ALTER FUNCTION pg_catalog.numeric_eq LEAKPROOF
Version 11.7.1 also fixes SIMILAR 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 from Postgres Pro Enterprise 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 the ALTER COLLATION "default" REFRESH VERSION command, as explained in ALTER COLLATION.
If you are upgrading from Postgres Pro Enterprise versions 11.11.x or lower and take PTRACK backups using pg_probackup, retake a full backup after upgrade.
To migrate from PostgreSQL, as well as Postgres Pro Standard or Postgres Pro Enterprise based on a previous PostgreSQL major version, see the migration instructions for version 11.