## E.40. Postgres Pro Standard 9.6.8.2

Release date: 2018-03-20

### E.40.1. Overview

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

Major enhancements over Postgres Pro Standard 9.6.8.1 include:

- Updated the pg_probackup utility from version 2.0.11 to 2.0.16, which includes the following new features:

  - Fixed an infinite loop that could happen during page validation.

  - Fixed segfault for the case of parallel `PTRACK` connections.

  - Allowed to use the `delete-wal` option without `delete-expired`.

  - Fixed CVE-2018-1058. Schema name is now explicitly used on every function call.

- You can now use `pgpro_build` function to get the latest commit ID for the source files of the current release.

- Fixed an issue with sort ordering of some Russian letters in the `mchar` module. Use `REINDEX DATABASE` command to update indexes.

### E.40.2. Migration to Version 9.6.8.2

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.7.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, as well as rename the `pgpro_build` function to `pgpro_source_id`. 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.