## Appendix E. Release Notes

The release notes contain the significant changes in each Postgres Pro release, with major features and migration issues listed at the top. The release notes do not contain changes that affect only a few users or changes that are internal and therefore not user-visible. For example, the optimizer is improved in almost every release, but the improvements are usually observed by users as simply faster queries.

A complete list of changes for each release can be obtained by viewing the Git logs for each release. The `pgsql-committers` email list records all source code changes as well. There is also a web interface that shows changes to specific files.

The name appearing next to each item represents the major developer for that item. Of course all changes involve community discussion and patch review, so each item is truly a community effort.

## E.1. Postgres Pro 9.6.3.2

### Release Date

2017-07-12

### E.1.1. Overview

This release is based on Postgres Pro 9.6.3.1 and PostgreSQL 9.6.3.

Major enhancements over Postgres Pro 9.6.3.1 include:

- Updated the pg_probackup backup manager to version 2.0 that includes the following new features:

  - Saving backups for different databases in a single backup catalog

    Storing backup data in a compressed state to save disk space

    Extended logging settings

- Added distribution for Debian 9.

- Added upstream patches that fix potential data corruption during freeze.

### E.1.2. Migration to Version 9.6.3.2

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.3.1.

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.