E.9. Postgres Pro 184.108.40.206
Release date: 2018-05-18
This release is based on PostgreSQL 9.5.13 and Postgres Pro 220.127.116.11. All improvements inherited from PostgreSQL 9.5.13 are listed in PostgreSQL 9.5.13 Release Notes.
Major enhancements over Postgres Pro 18.104.22.168 include:
pg_pathmanmodule to version 1.4.11. As compared to version 1.4.9, the following enhancements were introduced:
Fixed an issue with duplicate entries in query results for inherited tables. In general,
pg_pathmandoes not support multilevel partitioning.
Fixed a spurious
table is being partitioned nowerror raised by
Relaxed check constraint handling.
Fixed incorrect usage of
For a full list of changes, see pg_pathman Wiki.
Fixed an issue with pasting strings that include symbols of different character sets from clipboard to psql on Windows systems.
E.9.2. Migration to Version 22.214.171.124
Depending on your current installation, the upgrade procedure will differ.
If you are running Postgres Pro 126.96.36.199, it is enough to install the 188.8.131.52 version into the same directory. For earlier Postgres Pro versions, 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_upgradeis 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 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, perform a dump/restore using pg_dumpall.