E.29. Postgres Pro Standard 9.6.2.1
Release date: 2017-02-22
E.29.1. Overview
This release is based onPostgres Pro Standard9.6.1.2 andPostgreSQL9.6.2.
Major enhancements overPostgres Pro Standard 9.6.1.2 include:
Modulepg_pathman has been updated to version 1.3 (seeSection F.36.1.1).
Thesr_plan module is now initialized independently for each database instance.
Syntax for covering indexes has been changed. Now the keyword
INCLUDINGis replaced byINCLUDE. The previous syntax still works, but is deprecated (seeSection 11.6).RHEL-based distributions are installed in a separate location, so thePostgres Pro database can be installed in parallel with an existingPostgreSQL database.
Improved the algorithm of automatic TCP-port selection for the case of parallel installation of different versions of the product on Windows systems.
Updated thepg_probackup backup manager:
Added
retention showandretention purgecommands to implement retention policy.Added support for incremental backup of compressed page files. Compressed files are the feature of thePostgres Pro Enterprise.
Fixed
validatecommand. Thebackup_idparameter is optional now.
E.29.2. Migration to Version 9.6.2.1
A dump/restore usingpg_dumpall, or use ofpg_upgrade, is required for those wishing to migrate data from any previous major release.
A dump/restore is not required for those running 9.6.1.2.
However, if you are upgrading from vanilla 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 compiledPostgres Pro from source or create your database in a non-default location, runninginitdb manually, you should runpgpro_upgrade script provided in this distribution.
Before running the script, you should stop postgres service. Script should 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.