E.23. Postgres Pro Enterprise 11.7.1
Release date: 2020-02-28
E.23.1. Overview
This release is based on PostgreSQL 11.7 and Postgres Pro Enterprise 11.6.2. All changes inherited from PostgreSQL 11.7 are listed in PostgreSQL 11.7 Release Notes. As compared with Postgres Pro Enterprise 11.6.2, this version also provides the following changes:
Added the enable_compound_index_stats configuration parameter to control the use of compound indexes statistics for selectivity estimation.
Increased the maximum value of the track_activity_query_size parameter to 1MB. In vanilla PostgreSQL, this change is targeted for version 13.
Updated CFS to enhance compression functionality:
The
cfs_compress_small_relationsparameter controls whether small tables are compressed. It may be useful to turn off this setting for databases with many relations smaller than 1GB to avoid overhead.
The built-in connection pooler has been improved. As compared to the previous version, the following changes have been introduced:
The dedicated_users parameter enables you to specify one or more users that can have a separate backend for each connection even if connection pooling is enabled.
Pooled backends can now serve multiple users, so all connections to a particular database use a common pool.
Improved stability of multimaster extension:
It is recommended to use
multimasterin a three-node configuration, where one node is a referee. For details on how to set up a cluster with a referee, see Section F.30.3.3.Fixed an issue with WAL bloating by purging synchronization points of the dropped node and fixing the calculation of the minimal required LSN. Previously, it could occur when when dropping a cluster node.
Fixed an issue with returning a node to the cluster after this node has been offline for a long time.
Forced synchronization point upon
multimasterinitialization to handle the case when a crash happens before the first synchronization.
Fixed planner's optimization to correctly take into account similar
ORclauses if they reference columns that are different, but have the same position in different indexes.Improved query performance with row-level security policy enabled by correctly marking numeric comparison functions as leakproof.
Fixed self join removal functionality to achieve better stability.
Optimized execution of queries with Materialize nodes that return nothing; now such nodes are called only once and skipped in all the subsequent runs.
Fixed the
mcharextension to correctly handle theESCAPEclause inSIMILAR TOregular expressions.Upgraded pg_probackup to version 2.2.7.
Upgraded mamonsu to version 2.4.4.
E.23.2. Migration to Version 11.7.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.
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.