E.17. Postgres Pro Standard 10.5.1

Release Date: 2018-08-20

E.17.1. Overview

This release is based on PostgreSQL 10.5 and Postgres Pro Standard 10.4.1. All changes inherited from PostgreSQL 10.5 are listed in PostgreSQL 10.5 Release Notes. Other major changes and enhancements are as follows:

  • The pg_variables module now supports transactional variables. (See Section F.44.)

  • The auto_explain module can now display planning time.

  • Fixed a bug that made unusable some Hunspell dictionaries with FLAG num affixes, such as ru_aot.

  • Updated pg_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 ORPHAN status.

    • The show-config command now shows both modified pg_probackup parameters and the default settings that remained unchanged. The output can be formatted as JSON for better readability.

    • The restore command 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 the pg_probackup module.

E.17.2. Migration to Version 10.5.1

If you are upgrading from a Postgres Pro Standard version based on the same PostgreSQL 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 the REINDEX command for indexes that used mchar or mvarchar types. Besides, if you have been using pg_repack on Debian-based systems, you have to reinstall its package manually when upgrading to this version since its package got renamed to pg-repack-std-10.

To migrate from PostgreSQL or a Postgres Pro Standard release based on a previous PostgreSQL major version, see the instructions in Postgres 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.