## E.42. Postgres Pro Standard 9.6.7.1

Release date: 2018-02-14

### E.42.1. Overview

This release is based on PostgreSQL 9.6.7 and Postgres Pro Standard 9.6.6.1. All improvements inherited from PostgreSQL 9.6.7 are listed in PostgreSQL 9.6.7 Release Notes.

Major enhancements over Postgres Pro Standard 9.6.6.1 include:

- Updated `pg_pathman` module to version 1.4.9. This version fixes handling of `ONLY` in all kinds of queries. (See Section F.40 and Section F.40.1.1.)

- 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.42.2. Migration to Version 9.6.7.1

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

To upgrade from a Postgres Pro Standard 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.

To upgrade from a Postgres Pro Standard version based on the same PostgreSQL major release, a dump/restore is not required. If you are upgrading from Postgres Pro Standard 9.6.6.1, it is enough to install the new version into your current installation directory. When upgrading from Postgres Pro Standard 9.6.4.1 or lower, you must also use the `pgpro_upgrade` script provided in this distribution. This script updates metadata information to handle catalog number format change introduced after Postgres Pro Standard 9.6.4.1. If you are upgrading your Postgres Pro installation from a binary package, the `pgpro_upgrade` script is run automatically, unless 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). Running `pgpro_upgrade` as root will result in an error.

If you have compiled Postgres Pro from source code or created your database in a non-default location, you must run the `pgpro_upgrade` script manually.

### Note

On RPM-based Linux distributions, if you are upgrading from version 9.6.2.1 or lower, make sure to move the data directory from `pgsql` to the `pgpro` directory before running the `pgpro_upgrade` script.

To migrate from vanilla PostgreSQL 9.6.x, perform a dump/restore using pg_dumpall.