## E.49. Postgres Pro Standard 9.6.2.1

Release date: 2017-02-22

### E.49.1. Overview

This release is based on Postgres Pro Standard 9.6.1.2 and PostgreSQL 9.6.2.

Major enhancements over Postgres Pro Standard 9.6.1.2 include:

- Module pg_pathman has been updated to version 1.3 (see Section F.40.1.1).

- The sr_plan module is now initialized independently for each database instance.

- Syntax for covering indexes has been changed. Now the keyword `INCLUDING` is replaced by `INCLUDE`. The previous syntax still works, but is deprecated (see Section 11.6).

- RHEL-based distributions are installed in a separate location, so the Postgres Pro database can be installed in parallel with an existing PostgreSQL database.

- Improved the algorithm of automatic TCP-port selection for the case of parallel installation of different versions of the product on Windows systems.

- Updated the pg_probackup backup manager:

  - Added `retention show` and `retention purge` commands to implement retention policy.

  - Added support for incremental backup of compressed page files. Compressed files are the feature of the Postgres Pro Enterprise.

  - Fixed `validate` command. The `backup_id` parameter is optional now.

### E.49.2. Migration to Version 9.6.2.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 not required for those running 9.6.1.2.

However, if you are upgrading from vanilla 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 compiled Postgres Pro from source or create your database in a non-default location, running `initdb` manually, you should run `pgpro_upgrade` script provided in this distribution.

Before running the script, you should stop postgres service. Script should 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.