E.18. Postgres Pro Enterprise 9.6.9.2
Release date: 2018-07-03
E.18.1. Overview
This release is based on Postgres Pro Enterprise 9.6.9.1. It enables WAL reader to track timeline switches and use the up-to-date timeline, which is required for successful standby promotion.
E.18.2. Migration to Version 9.6.9.2
Depending on your current installation, the upgrade procedure will differ.
To upgrade from a Postgres Pro Enterprise version based on the same PostgreSQL major release, a dump/restore is not required. Instead of the pg_upgrade, you must use the pgpro_upgrade script provided in this distribution. This script updates metadata information to handle catalog number format change introduced in Postgres Pro Enterprise 9.6.4.1. If you are upgrading your Postgres Pro Enterprise installation from a binary package, the pgpro_upgrade script is run automatically, or you are prompted to run it manually.
Important
If you run pgpro_upgrade manually, you must stop 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.
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.
Note
On RPM-based Linux distributions, if you are upgrading from version 9.6.1.2, make sure to move the data directory from pgsql to the pgproee directory before running the pgpro_upgrade script.
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.