E.18. Postgres Pro Standard 9.6.10.1
Release date: 2018-08-20
E.18.1. Overview
This release is based onPostgreSQL 9.6.10 andPostgres Pro Standard 9.6.9.1. All improvements inherited fromPostgreSQL 9.6.10 are listed inPostgreSQL 9.6.10 Release Notes.
Major enhancements overPostgres Pro Standard 9.6.9.1 include:
The
pg_variablesmodule now supports transactional variables. (SeeSection F.44.)The
auto_explainmodule can now display planning time.Autovacuum now immediately drops orphaned temporary tables to prevent
pg_classbloating.Fixed a bug that made unusable some Hunspell dictionaries with
FLAG numaffixes, such asru_aot.Updatedpg_probackup module to version 2.0.19, which includes the following new features:
If one of its parent backups is corrupt, the incremental backup is marked with the
ORPHANstatus.The
show-configcommand now shows both modifiedpg_probackup parameters and the default settings that remained unchanged. The output can be formatted as JSON for better readability.The
restorecommand can now skip backup validation to speed up cluster recovery.Parallel execution of incremental backups has been improved.
You can merge incremental backups to their parent full backup to save disk space. This is an experimental feature that can cause backup corruption if the merge is interrupted.
Postgres Pro Standard version for Windows has been improved:
Lifted an implicit restriction on the number of simultaneously open files for each server subprocess.
Added an option to disable data checksums for your cluster. By default,Postgres Pro is installed with data checksums enabled.
E.18.2. Migration to Version 9.6.10.1
Depending on your current installation, the upgrade procedure will differ.
To upgrade from aPostgres Pro Standard version based on any previousPostgreSQL major release, make sure you have installed its latest minor version, and then perform a dump/restore usingpg_dumpall or use thepg_upgrade utility.
Important
When upgrading from versions 9.6.8.2 or lower, you must call theREINDEX command for indexes that usedmchar ormvarchar types.
To upgrade from aPostgres Pro Standard version based on the samePostgreSQL major release, a dump/restore is not required. If you are upgrading fromPostgres Pro Standard 9.6.7.1 or lower, you must also use thepgpro_upgrade script provided in this distribution. This script updates metadata information to handle catalog number format change introduced afterPostgres Pro Standard 9.6.4.1, as well as rename thepgpro_build function topgpro_source_id. If you are upgrading yourPostgres Pro installation from a binary package, thepgpro_upgrade script is run automatically, unless you are prompted to run it manually.
Important
If you runpgpro_upgrade manually, you must stop postgres service. The script must be run on behalf of the user owning the database (typically postgres). Runningpgpro_upgrade as root will result in an error. For details, seepgpro_upgrade.
If you have compiledPostgres Pro from source code or created your database in a non-default location, you must run thepgpro_upgrade script manually.
Note
On RPM-based Linux distributions, if you are upgrading from version 9.6.2.1 or lower, make sure to move the data directory frompgsql to thepgpro directory before running thepgpro_upgrade script.
To migrate from vanilla PostgreSQL 9.6.x, perform a dump/restore usingpg_dumpall.