E.25. Postgres Pro Enterprise 9.6.6.1
Release date: 2017-11-15
E.25.1. Overview
This release is based on PostgreSQL 9.6.6 and Postgres Pro Enterprise 9.6.5.2. All improvements inherited from PostgreSQL 9.6.6 are listed in PostgreSQL 9.6.6 Release Notes. Major enhancements over Postgres Pro Enterprise 9.6.5.2 include:
Improved multimaster extension. In particular, the following changes were introduced:
Added a new extension (referee) for managing quorum settings. With this extension, you can set up a standalone referee node for your cluster to assign the quorum status to a subset of nodes that constitutes half of the cluster. For details, see Section F.31.3.3.1.
Added a new parameter for choosing a major node in two-node clusters. You can now set up a major node that continues working even if there is no quorum. For details, see Section F.31.3.3.2.
Updated pg_pathman module to version 1.4.8. (See pg_pathman and Section F.39.1.1.) As compared to version 1.4.3, the following enhancements were introduced:
Improved cache invalidation mechanisms.
Disabled
COPYcommand. Usepartitioned_tableTOCOPY (SELECT * FROMinstead.partitioned_table) TOFixed
INSTEAD OFtriggers on views selected from partitioned tables.ALTER TABLEnow also renames auto naming sequences.partitioned_tableRENAME TODisabled some dangerous optimizations for
SELECT ... FOR SHARE/UPDATEon PostgreSQL 9.5.Improved error handling in concurrent partitioning background worker.
Prohibited execution of queries
DELETE FROMandpartitioned_table_1USINGpartitioned_table_2...UPDATEif such queries touch more than one partition ofpartitioned_table_1FROMpartitioned_table_2...partitioned_table_1.Fixed a bug causing crashes on
RESET ALL.Fixed
WHEREconditions that point to gaps between partitions.Restored compatibility with pg_repack.
For the full list of changes, see pg_pathman Wiki.
Updated the pg_probackup utility to version 2.0.11, which includes the following new features:
Password prompt interruption is now handled correctly.
The provided passwords are checked to be is non-empty.
The files that have not changed since the previous backup are not included into the next incremental backup.
Database version is now added into backup meta information.
Other miscellaneous bugfixes.
E.25.2. Migration to Version 9.6.6.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, 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.