## E.23. Postgres Pro Enterprise 9.6.4.1

Release date: 2017-08-16

### E.23.1. Overview

This release is based on Postgres Pro Enterprise 9.6.3.2 and Postgres Pro Standard 9.6.4.1.

Major enhancements over Postgres Pro Enterprise 9.6.3.2 include:

- Updated the pg_probackup backup manager to version 2.0

- Module pg_pathman updated to version 1.4.2

- In Compressed File System implementation, fixed a memory leak.

- Fixed potential data corruption in the online_analyze contrib module.

- Fixed `ALTER COLUMN` operation for tables with indexes.

- Improved multimaster extension:

  - Fixed `ALTER SYSTEM SET` command.

  - Fixed unexpected timeout of asynchronous connection.

  - Fixed invalid transaction state while walsender executing snapshot.

- Added primary key to schedule tables for the support of multimaster in pgpro_scheduler.

### E.23.2. Migration to Version 9.6.4.1

A dump/restore using pg_dumpall, or use of pg_upgrade, is required for those wishing to migrate data from any previous major release.

A dump/restore is required for those running Postgres Pro Enterprise 9.6.3.2, because catalog number format has been changed for better Postgres Pro Enterprise identification.

Dump/restore is necessary when migrating from PostgreSQL, Postgres Pro Standard, or Postgres Pro Enterprise edition.

For upgrades from previous releases of Postgres Pro Enterprise, Postgres Pro Standard, or PostgreSQL 9.6.x, some catalog changes should be applied.

If you use binary packages, and your database is in the default location, this upgrade should be performed automatically. If you've created your database in a non-default location, running `initdb` manually, you should run the `pgpro_upgrade` script provided in this distribution.

Before running the script, you should stop the `postgres` service. The script should be run on behalf of the user owning the database (typically `postgres`), and the `PGDATA` environment variable should be set to the directory where the database resides.