E.11. Postgres Pro Enterprise 9.6.15.1
Release date: 2019-08-13
E.11.1. Overview
This release is based on PostgreSQL 9.6.15 and Postgres Pro Enterprise 9.6.14.1. All improvements inherited from PostgreSQL 9.6.15 are listed in PostgreSQL 9.6.15 Release Notes. As compared with Postgres Pro Enterprise 9.6.14.1, this version also provides the following changes:
Added support for Debian 10.
Fixed
VACUUMlogic for truncating multixact members as required for 64-bit transaction and multixact IDs. It resolves a bloating issue that could affect thepg_multixactdirectory.Fixed replication issues that could occur with newly created GIN, GiST and SP-GiST indexes. Previously, the metapage of such indexes was not copied to standby after
CREATE INDEXorREINDEX, which caused an error if this index was accessed on standby before any other metapage updates.Improved planning accuracy for queries with
ORclauses. Now sorting is performed correctly for such queries.Fixed implementation of greater than (>) and not equal to (<>) operators for the
jsquerytype.Fixed a deadlock issue in the pg_wait_sampling module. Previously, a deadlock could occur if clients got disconnected before receiving the requested statistics on wait events. Now statistics collector releases the exclusive lock in such cases and logs the following message:
pg_wait_sampling collector: receiver of message queue has been detached.
E.11.2. Migration to Version 9.6.15.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.
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.