E.26. Postgres Pro Enterprise 9.6.5.2
Release date: 2017-10-16
E.26.1. Overview
This release is based on Postgres Pro Enterprise 9.6.5.1. Major enhancements over Postgres Pro Enterprise 9.6.5.1 include:
Updated pg_pathman module to version 1.4.7.
Updated pg_probackup utility to version 2.0.8.
Fixed a problem in compressed tablespace garbage collection with incompressible data.
Fixed handling of SIGTERM in pgpro_scheduler extension.
Fixed bugs in the aqo extension.
pgbench utility now continues to execute the script if a transaction is rolled back, and has an option to retry failed transactions several times.
Fixed incompatibility between pg_pathman and online_analyze extensions.
E.26.2. Migration to Version 9.6.5.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, as well as renames the pgpro_build function to pgpro_source_id. 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.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.