E.22. Postgres Pro Enterprise 11.7.2

Release date: 2020-04-07

E.22.1. Overview

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

  • Fixed a memory leak that could occur when vacuuming tables with non-unique B-tree indexes.

E.22.2. Migration to Version 11.7.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. When upgrading from these versions, run pg_upgrade to fix this issue, or manually correct pg_proc entries for these functions 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 if you are upgrading from lower versions.

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.