E.22. Postgres Pro Enterprise 9.6.7.1

Release date: 2018-02-16

E.22.1. Overview

This release is based on PostgreSQL 9.6.7 and Postgres Pro Enterprise 9.6.6.3. All improvements inherited from PostgreSQL 9.6.7 are listed in PostgreSQL 9.6.7 Release Notes. Major enhancements over Postgres Pro Enterprise 9.6.6.3 include:

  • Fixed handling of autonomous transactions in PL/Python.

  • Fixed compatibility of autonomous transactions with multimaster.

  • Added additional checks for suspend/resume functions in autonomous transactions.

  • Updated pgpro_scheduler module from to version 2.2. (See pgpro_scheduler.)

  • Fixed run-time plan statistics.

  • Fixed counting of parallel nodes.

  • Updated pg_wait_sampling module to version 1.1

  • Fixed DescribeLockTag() for 64-bit transaction identifiers.

  • Updated dump_stat module to version 1.1 that provides several bug fixes. (See dump_stat.)

  • Updated the PTRACK patch to version 1.4.

  • Implemented dynamic prepare of the psql history path on Windows systems.

  • Added support for TOAST to INCLUDED attributes for B-tree indexes.

E.22.2. Migration to Version 9.6.7.1

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.