E.16. Postgres Pro Standard 188.8.131.52
Release date: 2018-05-23
This release is based on PostgreSQL 9.6.9 and Postgres Pro Standard 184.108.40.206. All improvements inherited from PostgreSQL 9.6.9 are listed in PostgreSQL 9.6.9 Release Notes.
Major enhancements over Postgres Pro Standard 220.127.116.11 include:
Updated the Section F.29 to fix the sorting order for Cyrillic letters Yo and short I. Make sure to run the
REINDEXcommand to rebuild indexes that use
Updated the pg_probackup utility to version 2.0.17, which includes the following new features:
DELTAmode for incremental backups that reads all data files in the data directory and creates an incremental backup for pages that have changed since the previous backup.
New options for
--immediateoption ends recovery as soon as a consistent state is reached.
--recovery-target-actionoption specifies the action the server should take when the recovery target is reached.
--recovery-target-namespecifies a named savepoint up to which to restore the cluster data.
--write-recovery-confwrites a minimal
recovery.confin the output directory to facilitate setting up a standby server.
For details, see pg_probackup.
Updated PTRACK to version 1.6:
Now ptrack doesn't track unlogged relations.
Updated jsquery module.
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.
Performed multiple bug fixes in the shared_ispell module.
Improved Postgres Pro Standard version for Windows:
Fixed an issue with pasting strings that include symbols of different character sets from clipboard to psql on Windows systems.
Updated optimization algorithm for default database configuration.
You can now turn off configuration optimization when installing Postgres Pro from the command line by setting the
needoptimizationoption in the INI file to
E.16.2. Migration to Version 18.104.22.168
Depending on your current installation, the upgrade procedure will differ.
To upgrade from a Postgres Pro Standard version based on any previous PostgreSQL major release, make sure you have installed its latest minor version, and then perform a dump/restore using pg_dumpall or use the pg_upgrade utility.
When upgrading from versions 22.214.171.124 or lower, you must call the
REINDEX command for indexes that used
To upgrade from a Postgres Pro Standard version based on the same PostgreSQL major release, a dump/restore is not required. If you are upgrading from Postgres Pro Standard 126.96.36.199 or lower, you must also use the pgpro_upgrade script provided in this distribution. This script updates metadata information to handle catalog number format change introduced after Postgres Pro Standard 188.8.131.52, as well as rename the
pgpro_build function to
pgpro_source_id. If you are upgrading your Postgres Pro installation from a binary package, the
pgpro_upgrade script is run automatically, unless you are prompted to run it manually.
If you run
pgpro_upgrade manually, you must stop 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.
If you have compiled Postgres Pro from source code or created your database in a non-default location, you must run the
pgpro_upgrade script manually.
On RPM-based Linux distributions, if you are upgrading from version 184.108.40.206 or lower, make sure to move the data directory from
pgsql to the
pgpro directory before running the
To migrate from vanilla PostgreSQL 9.6.x, perform a dump/restore using pg_dumpall.