## E.15. Postgres Pro 9.6.0.1

Release date: 2016-10-12

### E.15.1. Overview

This release is based on PostgreSQL 9.6.0.

Major enhancements over PostgreSQL 9.6.0 include:

Core patches from Postgres Pro 9.5 has been applied:

- Covering indices patch by Anastasia Lubennikova (Commit: 91b4e25614247833d7960c49d783f69b90c0c149) (Details: http://www.postgresql.org/message-id/f90aa60a-b67f-95b5-d9f5-f5d8ced178c6@postgrespro.ru/

  ICU patch (Commit: ee711324f31cc039e656ea45c54abd0cf8ea3e41)

  Fixes to win32 build system (Commit: 84fa653ee00ebe54f591b18e3664fa6d5889224f)

  Added pgpro_version SQL function and appropriate defines into pg_config.h (Commit: 671a7525541aa3eece366dae4249aa43a56a2168)

  Integrated PTRACK patch (Commit: cea0987364070600fe640df0050d285b53cafb00)

  Added order by to index_including test to make 32-bit FreeBSD happy (Commit: fd9fc27d40b5dd4db611418bb848760154ec9f55)

Modules has been ported from Postgres Pro 9.5

- hunspell-dict (See Hunspell Dictionaries Modules)

- jsquery (See Section F.28)

- pg_variables (See Section F.51)

- pg_pathman (See Section F.40)

- pg_query_state (See Section F.43)

- shared-ispell (See shared_ispell)

- sr_plan (See sr_plan)

- dump_stat (See dump-stat)

Tools has been ported from Postgres Pro 9.5

- pg_arman

### E.15.2. Migration to Version 9.6.0.1

A dump/restore using pg_dumpall, or use of pg_upgrade, is required for those wishing to migrate data from any previous release.

Dump/restore is not necessary when migrating from PostgreSQL 9.6.x to Postgres Pro 9.6.x.y.

When upgrading from previous releases of Postgres Pro or 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 non-default location, running `initdb` manually, you should run `pgpro_upgrade` script provided in this distribution.

Before running script, you should stop postgres service. Script should be run as user, owning the database (typically postgres) and PGDATA environment variable should be set to the directory where database resides.