E.16. Postgres Pro Enterprise 9.6.10.2
Release date: 2018-09-17
E.16.1. Overview
This release is based on Postgres Pro Enterprise 9.6.10.1 and provides the following bug fixes and improvements:
Implemented the following changes in
pgbench:pgbenchnow supports compound commands.You can now limit the time allotted for transaction retries using the
--latency-limitoption. If this option is used together with--max-triesset to zero, transactions can be retried as many times as--latency-limitpermits.The reported TPS and the number of processed transactions now exclude skipped and failed transactions.
Updated
pg_pathmanmodule to version 1.4.14 to improve stability.Fixed
pgpro_upgradescript for Red Hat Enterprise Linux and SUSE systems so that it can be launched using a relative path.
E.16.2. Migration to Version 9.6.10.2
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.