E.19. Postgres Pro Enterprise 9.6.9.1
Release date: 2018-06-01
E.19.1. Overview
This release is based on PostgreSQL 9.6.9 and Postgres Pro Enterprise 9.6.8.2. All improvements inherited from PostgreSQL 9.6.9 are listed in PostgreSQL 9.6.9 Release Notes. Main changes over Postgres Pro Enterprise 9.6.8.2 include:
Fixed escaping rules for configuration variables in
multimaster.Updated pg_wait_sampling module to fix possible memory corruption on Windows.
Fixed memory issues of aqo module.
Fixed wrong calculation of delta during epoch shift.
Updated the mchar module to fix the sorting order for Cyrillic letters Yo and short I. Make sure to run the
REINDEXcommand to rebuild indexes that usemcharormvarchartypes.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
restoreandvalidatecommands:--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 minimalrecovery.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.
Updated
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 bypartition_table_concurrently().Relaxed check constraint handling.
Fixed incorrect usage of
memcpy()instart_bgworker().For a full list of changes, see pg_pathman Wiki.
Performed multiple bug fixes in the shared_ispell module.
Improved Postgres Pro Enterprise 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 to0.
E.19.2. Migration to Version 9.6.9.1
Depending on your current installation, the upgrade procedure will differ.
To upgrade from a Postgres Pro Enterprise version based on the same PostgreSQL major release, a dump/restore is not required. Instead of the pg_upgrade, you must use the pgpro_upgrade script provided in this distribution. This script updates metadata information to handle catalog number format change introduced in Postgres Pro Enterprise 9.6.4.1. If you are upgrading your Postgres Pro Enterprise installation from a binary package, the pgpro_upgrade script is run automatically, or you are prompted to run it manually.
Important
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) and PGDATA environment variable should be set to the directory where database resides. Running pgpro_upgrade as root will result in an error.
When upgrading from versions 9.6.8.2 or lower, you have to rebuild indexes that used mchar or mvarchar types.
When upgrading from versions 9.6.2.1 or lower, you have to rebuild GiST indexes built over columns of the intarray type.
Note
On RPM-based Linux distributions, if you are upgrading from version 9.6.1.2, make sure to move the data directory from pgsql to the pgproee directory before running the pgpro_upgrade script.
To migrate from vanilla PostgreSQL 9.6.x or Postgres Pro, make sure you have installed its latest minor version and then perform a dump/restore using pg_dumpall.