E.19. Postgres Pro Standard 10.5.3
Release Date: 2018-10-11
E.19.1. Overview
This release is based onPostgres Pro Standard 10.5.2 and provides the following improvements:
Added a fix for incorrect calculation of the minimum recovery point on standby servers, which could cause incorrect page references.
Updated theonline_analyze module, so that now it forbids nested
ANALYZEcalls.Increased the number of partitions of the shared buffer mapping hash table to 1024, which can improve performance on multi-core systems.
Fixed backup restore on a master server to avoid race conditions when applying two-phase transactions.
For Windows systems, fixed an issue with reloading dictionaries provided by the
shared_ispellmodule.Updatedpg_probackup to version 2.0.21, which provides the following bug fixes:
Issues related to restoring backups taken on standbys are resolved.
The
log-rotation-sizeandlog-rotation-ageparameters are now parsed correctly.The
showcommand now dynamically changes width of the displayed output to improve readability for large tables.The
restorecommand now correctly restores all symbolic links to tablespaces.If checksums are enabled, the
validatecommand now verifies checksums for blocks.
E.19.2. Migration to Version 10.5.3
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.