E.15. Postgres Pro Enterprise 11.11.3

Release date: 2021-04-05

E.15.1. Overview

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

  • Fixed an issue with an upgrade of Postgres Pro Enterprise 9.6 cluster to the current major version using pg_upgrade. Previously, it could crash when processing the free space map of a very large table.

  • Fixed the signed integer overflow in ptrack that could occur when ptrack map data in RAM was saved to disk. Previously, for large-size ptrack maps (ptrack.mapsize > 17200 MB), this resulted in a FATAL/ERROR ptrack checkpoint: stat_buf.st_size != ptrack_map_size XXX != YYY error during a checkpoint.

  • Fixed building of covering indexes with included columns of type for which the collation is defined in the table. The fixed defect could result in an ERROR: could not determine which collation to use for string comparison error during the ANALYZE operation on the table, although single columns could be successfully analyzed. To avoid this error in future, after upgrading, rebuild covering indexes built at least with one included column.

E.15.2. Migration to Version 11.11.3

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.

When upgrading from Postgres Pro Enterprise versions 11.11.2 or lower, rebuild covering indexes containing at least one included column of type for which the collation was defined in the table.

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.