## E.4. Postgres Pro Enterprise 9.6.9.1

Release date: 2018-06-01

### E.4.1. Overview

This release is based on Postgres Pro Standard 9.6.9.1 and Postgres Pro Enterprise 9.6.8.2. All improvements inherited from Postgres Pro Standard 9.6.9.1 are listed in Postgres Pro Standard 9.6.9.1 Release Notes.

Main changes over Postgres Pro Enterprise 9.6.8.2 include:

- Fixed an issue with GiST indexes on columns of the `intarray` type. Make sure to run the `REINDEX` command to rebuild GiST and SP-GiST indexes.

- Fixed escaping rules for configuration variables in `multimaster`.

- Updated pg_wait_sampling module to fix possible memory corruption on Windows.

- Fixed memory issues of aqo module.

- Fixed wrong calculation of delta during epoch shift.

### E.4.2. Migration to Version 9.6.9.1

Depending on your current installation, the upgrade procedure will differ.

To upgrade from a Postgres Pro Enterprise version based on any previous PostgreSQL major release, you can perform a dump/restore using pg_dumpall, or use the pg_upgrade utility. The first option is safer, while the second is faster and can significantly speed up the upgrade process for large databases.

### Important

When upgrading from versions 9.6.8.2 or lower, you must call the `REINDEX` command for indexes that used `mchar` or `mvarchar` types.

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.

### 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, perform a dump/restore using pg_dumpall.