E.18. Postgres Pro Standard 10.6.1
Release Date: 2018-11-20
E.18.1. Overview
This release is based onPostgreSQL 10.6 andPostgres Pro Standard 10.5.3. All changes inherited fromPostgreSQL 10.6 are listed inPostgreSQL 10.6 Release Notes. Other major changes and enhancements are as follows:
Added support for Ubuntu 18.10, Astra Linux Smolensk 1.6, and Red OS Murom 7 operating systems.
Updatedpg-setup:
This script can now initialize the database cluster in a non-default location and store the corresponding
PGDATAvalue in a system configuration file.You can now runpg-setup with the
setoption to modify cluster configuration.
Enabled NUL byte replacement with the specified ASCII code while loading data using the
COPY FROMcommand. Seenul_byte_replacement_on_import parameter description for details.Upgraded the
amcheckextension to version 1.1.Improvedplantuner stability and fixed a memory leak.
Planning for queries with multiple
ORoperators in theWHEREclause has been improved.Updated
pg_pathmanmodule to version 1.5.2. As compared to version 1.4.14 provided in the previousPostgres Pro releases, the following enhancements were introduced:Added support for multilevel partitioning.
Eliminated update triggers and added
pg_pathman.enable_partitionrouterparameter to enable/disable cross-partition updates.Renamed
get_pathman_lib_version()topathman_version().Provided other miscellaneous bug fixes and improvements. For a full list of changes, seepg_pathman Wiki.
Updated
pg_probackupmodule to version 2.0.24. As compared to version 2.0.19 provided in the previousPostgres Pro releases, the following enhancements were introduced:If unchanged since the previous backup, files that do not store relation data are now skipped in incremental backups.
Version number specified in
pg_probackup.confis now preserved when this file gets updated, which allows to correctly identifypg_probackup version used to take the backup.Fixed an issue with restoring compressed file blocks and enhanced checks for compression errors. Previously,pg_probackup could not restore file blocks that the
zlibalgorithm failed to compress during backup. This issue could not be detected by the built-inpg_probackup validation mechanism as it occurs on a lower level that validation itself. You are recommended to re-validate existing backups using thispg_probackup version.Improved validation algorithm. Files are now validated block by block by default, not only in case of file-level checksum mismatch. You can disable this behavior using the
--skip-block-validationoption.Allowed restarting a backup merge if the previous attempt has been interrupted.
Allowed taking backups from standby servers without connecting to the master. Besides,pg_probackup now uses its built-in mechanism to determine the consistency point, so there is no risk that backups from standby contain any inconsistent data.
Introduced the following changes for Windows version ofPostgres Pro:
PL/Perl now requires ActivePerl 5.26.
32-bitPostgres Pro version is no longer provided.
E.18.2. Migration to Version 10.6.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.