## E.2. Postgres Pro Enterprise 9.6.10.1

Release date: 2018-08-31

### E.2.1. Overview

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

Main changes over Postgres Pro Enterprise 9.6.9.2 are as follows:

- On Debian-based systems, library packages `libecpg-compat3`, `libecpg6`, `libecpg-dev`, `libpgtypes3`, `libpq5`, `libpq-dev` provided with Postgres Pro Enterprise got renamed and now have a `postgrespro-` prefix. When upgrading from a previous version of Postgres Pro Enterprise, run `apt-get dist-upgrade` to handle this change in an automated way, or install the new packages manually.

- Updated pg_pathman module to version 1.4.13. For a full list of changes, see pg_pathman Wiki.

- Log files now include the number of rows and the size of the data passed to the client if `log_duration` is enabled or if the query runs longer than `log_min_duration_statement`.

- The compress_temp_relations variable enables/disables compression of temporary tables.

- Miscellaneous bug fixes.

### E.2.2. Migration to Version 9.6.10.1

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

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

To upgrade from a Postgres Pro Enterprise version based on the same PostgreSQL major release, a dump/restore is not required. It is usually enough to install the new version into the same installation directory. Once the new binaries are installed, the `pgpro_upgrade` script is run automatically to check whether additional setup is required and complete the upgrade.

When upgrading from version 9.6.9.1 or lower, you must run the `REINDEX` command to rebuild GiST and SP-GiST indexes.

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

When upgrading from version 9.6.1.2 on RPM-based Linux distributions, make sure to move the data directory from `pgsql` to the `pgproee` directory before running the `pgpro_upgrade` script.

For some Linux distributions, you may be prompted to run `pgpro_upgrade` manually. In this case, you must stop the `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. This step is not required when upgrading from version 9.6.4.1 or higher.