E.23. Postgres Pro Enterprise 9.6.6.3
Release date: 2018-01-17
E.23.1. Overview
This release is based on Postgres Pro Enterprise 9.6.6.2. Major enhancements over Postgres Pro Enterprise 9.6.6.2 include:
Improved multimaster extension. In particular, the following changes were introduced:
Fixed rules of resolving stale prepared transactions after a node failure.
Fixed errors that occurred when selecting transactions to apply during automatic recovery process.
TRUNCATEoperations now do not cause global cluster locks.Sped up node status switches.
Referee decision is now preserved after rebooting the nodes that won the referee voting.
Updated pg_pathman module to version 1.4.9. For a full list of changes, see pg_pathman Wiki.
Added several fixes for 64-bit XIDs.
Improved k-NN support:
Fixed the execution of the following query types with a btree index:
SELECT * FROM tab WHERE col IN (1,2,3) ORDER BY col <-> 4
Added cross-type distance operators, such as int2 <-> int4, float4 <-> float8, date <-> timestamp, etc.
Added the
ammatchorderbyopmethod.Enabled distance recheck for SP-GiST indexes. For details, see the description of the
leaf_consistentfunction in Section 60.3.
Updated RUM index to version 1.2 (See Section F.55.)
Added support for the
anyarraytype viarum_anyarray_opsandrum_anyarray_addon_opsoperator classes.
Updated pg_probackup utility to version 2.0.14.
Fixed race conditions in
ptrackand page backups.Fixed parallel
ptrackbackup interruption.Added new backup state
ORPHAN, which indicates that one of previous backups is corrupted.
E.23.2. Migration to Version 9.6.6.3
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, as well as renames the pgpro_build function to pgpro_source_id. 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.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.