## E.2. Postgres Pro 9.5.15.1

Release date: 2018-11-16

### E.2.1. Overview

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

Major enhancements over Postgres Pro Standard 9.5.14.1 include:

- Fixed an issue in index search that caused a slowdown when using complex `jsquery` values.

- For Windows systems, fixed an issue with reloading dictionaries provided by the `shared_ispell` module.

- Updated `pg_pathman` module to version 1.5.2. As compared to version 1.4.14 provided in the previous Postgres Pro releases, the following enhancements were introduced:

  - Added support for multilevel partitioning.

  - Eliminated update triggers and added `pg_pathman.enable_partitionrouter` parameter to enable/disable cross-partition updates.

  - Renamed `get_pathman_lib_version()` to `pathman_version()`.

  - Provided other miscellaneous bug fixes and improvements. For a full list of changes, see pg_pathman Wiki.

- Introduced the following changes for Windows version of Postgres Pro:

  - PL/Perl now requires ActivePerl 5.26.

  - 32-bit Postgres Pro version is no longer provided.

### E.2.2. Migration to Version 9.5.15.1

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

If you are running Postgres Pro Standard version 9.5.3.2 or higher, it is enough to install the 9.5.15.1 version into the same directory. However, if you are upgrading from PostgreSQL 9.5.x or lower versions of Postgres Pro Standard, some catalog changes should be applied, so pgpro_upgrade script is required to complete the upgrade:

- If you are upgrading your installation from a binary package, and your database is in the default location, `pgpro_upgrade` is run automatically, unless you are prompted to run it manually.

- If you compiled Postgres Pro from source code or created your database in a non-default location, you must run `pgpro_upgrade` script manually.

### Important

Before launching `pgpro_upgrade` manually, you must stop the `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. For details, see pgpro_upgrade.

To migrate to this version from vanilla PostgreSQL 9.5.4 or lower, perform a dump/restore using pg_dumpall.