E.15. Postgres Pro Enterprise 11.12.1
Release date: 2021-06-07
E.15.1. Overview
This release is based on PostgreSQL 11.12 and Postgres Pro Enterprise 11.11.3. All changes inherited from PostgreSQL 11.12 are listed in PostgreSQL 11.12 Release Notes. As compared with Postgres Pro Enterprise 11.11.3, this version also provides the following changes:
Fixed a bug in the rum extension which caused phrase search to return less results than expected when the
rum_tsvector_addon_opsorrum_tsvector_hash_addon_opsoperator class was used.Fixed a bug in B-tree deduplication that could lead to a loss of index entries following a single dead entry, thus breaking the index.
Optimized writing of empty pages to
*.cfmfiles when upgrading a cluster with compressed tablespaces using pg_upgrade.Removed the
hunspell_ne_npHunspell dictionary. If you still need it, use the extension from github.Fixed an issue that could lead to a server crash due to dangling pointers to the statistics data when using autonomous transactions.
Upgraded PTRACK to use a different algorithm for tracking changed pages. This greatly reduces the number of false positives among the changed pages tracked in the PTRACK map and hence the size of PTRACK backups.
Fixed a memory leak in B-tree deduplication.
Implemented restoration of corrupted WAL data from in-memory WAL buffers. This is controlled by the wal_sender_check_crc parameter.
Removed the legacy pg_shardman extension.
Fixed a bug that caused queries to fail with an error “geqo failed to make a valid plan” after updating statistics with
VACUUM ANALYZEwhenenable_compound_index_statswas on.Dropped support for the multimaster extension.
Ended support for Ubuntu 16.04.
Fixed an issue of installing Postgres Pro on Alt Linux 8.2 SP. For this OS, Postgres Pro now provides a separate package repository, which is different from the repositories of earlier Alt Linux SP versions.
Upgraded pg_hint_plan.
Improved the planner's algorithm of self-join selectivity calculation, which ensures more accurate estimates of the number of rows after joins.
Upgraded mamonsu to version 2.7.1.
Upgraded pgpro_controldata to version 13.2.0.
E.15.2. Migration to Version 11.12.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.
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.