E.26. Postgres Pro Standard 188.8.131.52
Release date: 2017-02-22
Major enhancements over Postgres Pro Standard 184.108.40.206 include:
The sr_plan module is now initialized independently for each database instance.
Syntax for covering indexes has been changed. Now the keyword
INCLUDINGis replaced by
INCLUDE. The previous syntax still works, but is deprecated (see Section 11.6).
RHEL-based distributions are installed in a separate location, so the Postgres Pro database can be installed in parallel with an existing PostgreSQL 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 the pg_probackup backup manager:
retention purgecommands to implement retention policy.
Added support for incremental backup of compressed page files. Compressed files are the feature of the Postgres Pro Enterprise.
backup_idparameter is optional now.
E.26.2. Migration to Version 220.127.116.11
A dump/restore is not required for those running 18.104.22.168.
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 compiled Postgres Pro from source or create your database in a non-default location, running
initdb manually, you should run
pgpro_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.