E.3. Postgres Pro Enterprise 9.6.22.1
Release date: 2021-06-01
E.3.1. Overview
This release is based on PostgreSQL 9.6.22 and Postgres Pro Enterprise 9.6.21.1. All improvements inherited from PostgreSQL 9.6.22 are listed in PostgreSQL 9.6.22 Release Notes. As compared with Postgres Pro Enterprise 9.6.21.1, 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 an issue that could lead to a server crash due to dangling pointers to the statistics data when using autonomous transactions.
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.
Implemented restoration of corrupted WAL data from in-memory WAL buffers. This is controlled by the wal_sender_check_crc parameter.
Dropped support for the multimaster extension.
Ended support for Ubuntu 16.04.
Upgraded pg_hint_plan.
Upgraded mamonsu to version 2.7.1.
Upgraded pgpro_controldata to version 13.2.0.
E.3.2. Migration to Version 9.6.22.1
Depending on your current installation, the upgrade procedure will differ.
To migrate from vanilla PostgreSQL 9.6.x or Postgres Pro Standard, make sure you have installed its latest minor version and then perform a dump/restore using pg_dumpall. Besides, make sure to pay special attention to implementation specifics of 64-bit transaction IDs. If you have used explicit casts to 32-bit integers when handling transaction IDs, you have to replace them with casts to bigint since 64-bit transaction IDs are of the bigint type.
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 9.6.16.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 9.6.17.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
To upgrade from a Postgres Pro Enterprise version based on the same PostgreSQL major release, a dump/restore is not required. It is usually enough to install the new version into the same installation directory. Once the new binaries are installed, the pgpro_upgrade script is run automatically to check whether additional setup is required and complete the upgrade.
Since pg_probackup delivery model changed in Postgres Pro Enterprise 9.6.12.1, when upgrading from a lower version on ALT Linux and Debian-based systems, run apt dist-upgrade (or apt-get dist-upgrade) to ensure that all new dependencies are handled correctly. On Windows, you have to run a separate pg_probackup installer to complete the upgrade.
When upgrading from versions 9.6.9.1 through 9.6.14.1, you must run the REINDEX command to rebuild GIN, GiST, and SP-GiST indexes to fix replication issues that could be observed in these versions. You should also retake all backups for these versions if your database had such indexes.
When upgrading from versions 9.6.8.2 or lower, you have to rebuild indexes that used mchar or mvarchar types.
When upgrading from versions 9.6.2.1 or lower, you have to rebuild GiST indexes built over columns of the intarray type.
When upgrading from version 9.6.1.2 on RPM-based Linux distributions, make sure to move the data directory from pgsql to the pgproee directory before running the pgpro_upgrade script.
For some Linux distributions, you may be prompted to run pgpro_upgrade manually. In this case, you must stop the postgres service. The script must be run on behalf of the user owning the database (typically postgres) and PGDATA environment variable should be set to the directory where database resides. Running pgpro_upgrade as root will result in an error. This step is not required when upgrading from version 9.6.4.1 or higher.