E.17. Postgres Pro Enterprise 11.11.2

Release date: 2021-03-23

E.17.1. Overview

This release is based on Postgres Pro Enterprise 11.11.1 and provides the following changes:

  • Fixed an issue with upgrading Postgres Pro Enterprise 9.6 cluster to the current major version of Postgres Pro Enterprise. Previously, such an upgrade could result in a corrupted free space map and visibility map; the corruption manifested in could not read block XXX in file ... errors.

  • Fixed incorrect data conversion after Postgres Pro Enterprise cluster upgrade through pg_upgrade following a migration from PostgreSQL or Postgres Pro Standard edition. Previously, a cluster repeatedly converted like this would lose its original conversion attribute, which would result in a serious data corruption unless all the data was accessed before the second upgrade.

  • Added the log2_num_lock_partitions parameter which allows to change a number of lock partitions. Previously the shared lock tables were always divided into 16 partitions; now this number can be increased up to 256 to prevent performance loss in some special cases.

E.17.2. Migration to Version 11.11.2

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.

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.

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.