E.21. Postgres Pro Standard 10.5.1
Release Date: 2018-08-20
E.21.1. Overview
This release is based onPostgreSQL 10.5 andPostgres Pro Standard 10.4.1. All changes inherited fromPostgreSQL 10.5 are listed inPostgreSQL 10.5 Release Notes. Other major changes and enhancements are as follows:
The
pg_variablesmodule now supports transactional variables. (SeeSection F.44.)The
auto_explainmodule can now display planning time.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:
You can now restore the cluster up to the specified LSN.
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.
Added support for thepg_probackup module.
E.21.2. Migration to Version 10.5.1
If you are upgrading from aPostgres Pro Standard version based on the samePostgreSQL major release, it is enough to install the new version into your current installation directory.
When upgrading from version 10.3.2 or lower, you must call theREINDEX command for indexes that usedmchar ormvarchar types. Besides, if you have been usingpg_repack on Debian-based systems, you have to reinstall its package manually when upgrading to this version since its package got renamed topg-repack-std-10.
To migrate fromPostgreSQL or aPostgres Pro Standard release based on a previousPostgreSQL major version, see the instructions inPostgres Pro Standard 10.1.1 Release Notes. If you are opting for a dump/restore, make sure to use the--add-collprovider option to correctly choose the provider for the default collation of the migrated database.