E.30. Postgres Pro Enterprise 9.6.3.1
Release date: 2017-05-25
E.30.1. Overview
This release is based on Postgres Pro Enterprise 9.6.2.1 and PostgreSQL 9.6.3 Major enhancements over Postgres Pro Enterprise 9.6.2.1 include:
Fixed an issue with GiST indexes on columns of the
intarraytype. Make sure to run theREINDEXcommand to rebuild such indexes.Updated the pg_probackup backup manager to version 1.1.11. Command-line interface has been changed.
Improved multimaster extension:
Added support for savepoints.
Extended support for DDL statements.
(See Section F.31.)
Enabled support for multiple data types in RUM index, such as
int,bigint,float,time,interval,bytea,text, and more. You can now storetsvectortype together with other types in a single index.(See Section F.55.)
Improved autonomous transaction support:
Fixed handling of multixact IDs.
Speeded up execution of autonomous transactions.
(See Chapter 16.)
Added pg_tsparser extension for text search.
In addition to separate word parts returned by default, pg_tsparser also returns the whole word if this word includes:
underscores
numbers and letters separated by the hyphen character
Updated the pg_pathman module to version 1.3.2. This version provides compatibility fixes for this release.
The sr_plan module is now working with non-default
search_pathvariable.Fixed WAL inconsistency bug in covering indexes.
Added distribution for SUSE Linux Enterprise Server 12 SP1 and Ubuntu 17.04.
Applied patches to optimize inheritance.
Updated PTRACK patch to version 1.2.
Provided performance improvements for queries typical for 1C solutions.
E.30.2. Migration to Version 9.6.3.1
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.