E.29. Postgres Pro Enterprise 9.6.3.2
Release date: 2017-06-28
E.29.1. Overview
This release is based on Postgres Pro Enterprise 9.6.3.1. Major enhancements over Postgres Pro Enterprise 9.6.3.1 include:
Updated RUM index to version 1.1 (See Section F.55.)
In Compressed File System (CFS), fixed a bug caused by invalid merge, as well as included many other fixes.
Improved multimaster extension:
Fixed replication issues and other issues caused by running the
mtm.make_table_localfunction.Added the
multimaster.major_nodevariable. With this variable set totruethe cluster node can continue working even if connection to the majority of the nodes is lost.
Fixed an issue with pgpro_scheduler background worker hanging at the scheduled job startup for cases when one of the critical tables is locked.
Fixed an issue with deleting functions declared in languages that do not have the
validatemethod (for example, inPL/TCL).
E.29.2. Migration to Version 9.6.3.2
A dump/restore using pg_dumpall, or use of pg_upgrade, is required for those wishing to migrate data from any previous major release.
Dump/restore is necessary when migrating from PostgreSQL, Postgres Pro Standard, or Postgres Pro Enterprise edition.
For upgrades from previous releases of Postgres Pro Enterprise, Postgres Pro Standard, or PostgreSQL 9.6.x, some catalog changes should be applied.
If you use binary packages, and your database is in the default location, this upgrade should be performed automatically. If you've created your database in a non-default location, running initdb manually, you should run the pgpro_upgrade script provided in this distribution.
Before running the script, you should stop the postgres service. The script should be run on behalf of the user owning the database (typically postgres), and the PGDATA environment variable should be set to the directory where the database resides.
When upgrading from versions 9.6.2.1 or lower, you have to rebuild GiST indexes built over columns of the intarray type.