E.14. Postgres Pro Enterprise 9.6.11.1
Release date: 2018-11-20
E.14.1. Overview
This release is based on PostgreSQL 9.6.11 and Postgres Pro Enterprise 9.6.10.3. All improvements inherited from PostgreSQL 9.6.11 are listed in PostgreSQL 9.6.11 Release Notes. As compared with Postgres Pro Enterprise 9.6.10.3, this version also provides the following changes:
Added support for Astra Linux Smolensk 1.6.
Improved stability of autonomous transactions.
For Windows systems, fixed an issue with reloading dictionaries provided by the
shared_ispellmodule.Improved planning for queries with multiple
ORoperators in theWHEREclause.Fixed an issue in index search that caused a slowdown when using complex
jsqueryvalues.Improved plantuner stability and fixed a memory leak.
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.
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.14.2. Migration to Version 9.6.11.1
Depending on your current installation, the upgrade procedure will differ.
To migrate from vanilla PostgreSQL 9.6.x or Postgres Pro Standard, make sure you have installed its latest minor version and then perform a dump/restore using pg_dumpall.
To upgrade from a Postgres Pro Enterprise version based on the same PostgreSQL major release, a dump/restore is not required. It is usually enough to install the new version into the same installation directory. Once the new binaries are installed, the pgpro_upgrade script is run automatically to check whether additional setup is required and complete the upgrade.
When upgrading from versions 9.6.8.2 or lower, you have to rebuild indexes that used mchar or mvarchar types.
When upgrading from versions 9.6.2.1 or lower, you have to rebuild GiST indexes built over columns of the intarray type.
When upgrading from version 9.6.1.2 on RPM-based Linux distributions, make sure to move the data directory from pgsql to the pgproee directory before running the pgpro_upgrade script.
For some Linux distributions, you may be prompted to run pgpro_upgrade manually. In this case, you must stop the postgres service. The script must be run on behalf of the user owning the database (typically postgres) and PGDATA environment variable should be set to the directory where database resides. Running pgpro_upgrade as root will result in an error. This step is not required when upgrading from version 9.6.4.1 or higher.