E.9. Postgres Pro Enterprise 11.17.1
Release date: 2022-09-02
E.9.1. Overview
This release is based on PostgreSQL 11.17 and Postgres Pro Enterprise 11.16.1. All changes inherited from PostgreSQL 11.17 are listed in PostgreSQL 11.17 Release Notes. As compared with Postgres Pro Enterprise 11.16.1, this version also provides the following changes:
Fixed an issue with a large number of warnings issued during page conversion after the upgrade of Postgres Pro Enterprise 9.6 cluster to the current major version. Now
pd_prune_xidvalues of version-9.6 pages are reset to zero.Fixed a bug in the logic of epoch shifting, which didn't take into account the
XMAX_INVALIDhint bit of the tuple. Previously, it could lead to a sudden increase of the current transaction ID.Resolved an issue that caused an error “duplicate key value violates unique constraint” when indexing a database in multiple threads. Now the chosen name of a type being created for the index gets locked to avoid choosing the same name in a parallel process.
Resolved an issue in the planner's use of the compound indexes statistics: the optimizer reduced the cost prediction accuracy for a query plan if in the
WHEREclause of the query, values of different types were compared (for example:integerandnumeric,textandname). Sometimes, for certain combinations of the compared types and values, the issue could cause a server crash.Upgraded mamonsu to version 3.5.1. Notable changes are as follows:
Resolved the security issue of exposing passwords through the configuration file. Only
mamonsuuser can accessagent.confnow.Fixed metrics computation that caused “float division by zero” errors in the mamonsu STATEMENTS plugin.
Upgraded pg_probackup to version 2.5.7, which provides the following new features and bugfixes:
Enabled output of logs in the JSON format by adding new logging options.
Added an option to explicitly specify the directory where the
restorecommand should restore WAL records.Changed the level of detail of logging some messages of pg_probackup commands to add user convenience to reading logs.
Fixed pg_probackup hanging that could occur when the
ControlMasteroption was specified in the SSHconfigfile. Now the value ofControlMasteris explicitly set to “no”.
E.9.2. Migration to Version 11.17.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.