E.25. Postgres Pro Enterprise 10.6.1
Release date: 2018-10-20
E.25.1. Overview
This release is based on PostgreSQL 10.6 and Postgres Pro Enterprise 10.5.3. All changes inherited from PostgreSQL 10.6 are listed in PostgreSQL 10.6 Release Notes. As compared with Postgres Pro Enterprise 10.5.3, this version also provides the following changes:
Added support for Astra Linux Smolensk 1.6.
Improved stability of autonomous transactions.
Updated pg-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 run pg-setup with the
setoption to modify cluster configuration.
Improved planning for queries with multiple
ORoperators in theWHEREclause.Upgraded the
amcheckextension to version 1.1.Improved plantuner stability and fixed a memory leak.
Fixed an issue in index search that caused a slowdown when using complex
jsqueryvalues.Added seq_scan_startup_cost_first_row parameter that allows to better prioritize sequential and index scans.
Added lwlock_shared_limit parameter that enables fair lightweight lock scheduling after the specified number of shared locks is acquired.
Enabled NUL byte replacement with the specified ASCII code while loading data using the
COPY FROMcommand. See nul_byte_replacement_on_import parameter description for details.For Windows systems, fixed an issue with reloading dictionaries provided by the
shared_ispellmodule.Updated
pg_pathmanmodule to version 1.5.2. As compared to version 1.4.14 provided in the previous Postgres 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, see pg_pathman Wiki.
Updated
pg_probackupmodule to version 2.0.24. As compared to version 2.0.19 provided in the previous Postgres 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 identify pg_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-in pg_probackup validation mechanism as it occurs on a lower level that validation itself. You are recommended to re-validate existing backups using this pg_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.
Updated
pgpro_schedulerto version 2.3, which implements logging of all scheduling changes. To enable this functionality, you have to set the schedule.enable_history parameter totrue.Introduced the following changes for Windows version of Postgres Pro:
PL/Perl now requires ActivePerl 5.26.
32-bit Postgres Pro version is no longer provided.
E.25.2. Migration to Version 10.6.1
If you are upgrading from a Postgres Pro Enterprise version based on the same PostgreSQL major release, it is enough to install the new version into your current installation directory.
Important
When upgrading from versions 10.3.3 or lower, you have to rebuild GiST indexes built over columns of the intarray type, as well as indexes that use mchar or mvarchar types.
To migrate from PostgreSQL, as well as Postgres Pro Standard or Postgres Pro Enterprise based on a previous PostgreSQL major version, see the migration instructions for version 10. 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.