E.15. Postgres Pro Enterprise 9.6.10.3
Release date: 2018-10-11
E.15.1. Overview
This release is based on Postgres Pro Enterprise 9.6.10.2 and provides the following improvements:
pgbadgernow supports the extended log format ofPostgres Pro Enterprise. Its package got renamed topgpro-pgbadger.
Added a fix for incorrect calculation of the minimum recovery point on standby servers, which could cause incorrect page references.
Updated the online_analyze module, so that now it forbids nested
ANALYZEcalls.Increased the number of partitions of the shared buffer mapping hash table to 1024, which can improve performance on multi-core systems.
Added
amcheckmodule that allows you to verify logical consistency of the structure of indexes. (See amcheck for details.)Fixed backup restore on a master server to avoid race conditions when applying two-phase transactions.
For Windows systems, fixed an issue with reloading dictionaries provided by the
shared_ispellmodule.Updated pg_probackup to version 2.0.21, which provides the following bug fixes:
Issues related to restoring backups taken on standbys are resolved.
The
log-rotation-sizeandlog-rotation-ageparameters are now parsed correctly.The
showcommand now dynamically changes width of the displayed output to improve readability for large tables.The
restorecommand now correctly restores all symbolic links to tablespaces.If checksums are enabled, the
validatecommand now verifies checksums for blocks.
E.15.2. Migration to Version 9.6.10.3
Depending on your current installation, the upgrade procedure will differ.
To migrate from vanilla PostgreSQL 9.6.x or Postgres Pro, 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.
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.