E.17. Postgres Pro Standard 10.7.1
Release Date: 2019-03-27
E.17.1. Overview
This release is based onPostgreSQL 10.7 andPostgres Pro Standard 10.6.1. All changes inherited fromPostgreSQL 10.7 are listed inPostgreSQL 10.7 Release Notes. Other major changes and enhancements are as follows:
Fixed processing of queries with multiple
ORclauses to eliminate duplicate results and ensure the correct sort order.Fixed an issue that could cause server failures when using non-strict aggregate functions.
Changed delivery model forpg_probackup utility:
On Linux,pg_probackup is now provided in the
pg-probackup-std-10package. On ALT Linux and Debian-based systems, when upgrading fromPostgres Pro Standard 10.6.1 or lower, runapt dist-upgrade(orapt-get dist-upgrade) to ensure that all new dependencies are handled correctly.On Windows,pg_probackup now has a separate installer. You have to install core components of the currentPostgres Pro version before installingpg_probackup.
Added new options toPostgres Pro interactive installer for Windows. Now you can:
Choose
icuorlibcas the provider for the default collation. Previously,Postgres Pro Standard always usedicuby default.Select a Windows user that startsPostgres Pro service. By default,Postgres Pro service is started on behalf of
NT AUTHORITY\NetworkService.
On SUSE Linux Enterprise Server and RHEL-based systems, moved several utilities to different packages for consistency with other Linux distributions:pg_receivewal andpg_recvlogical are delivered as part of the
postgrespro-std-10-clientpackage, whilepg_rewind,pg_waldump,pg_upgrade are now located in thepostgrespro-std-10-serverpackage.Backported the patch that addresses
dsm_attach()race condition when DSM handles are reused; in vanillaPostgreSQL, this fix is targeted for the future updates only. The patch is hoped to resolve issues when the server reports the following error message:ERROR: dsa_area could not attach to segment.Fixedpg_upgrade to avoid issues with domain constraints that depend on collations. Such constraints are now validated during the upgrade, while in the the previousPostgres Pro versions they were always marked as invalid in the new cluster.
Fixed thepg-setup script so that it can initialize a cluster in a non-default location when run with the
-Doption.Changes in
rumandbloomindexes are now tracked correctly bypg_probackup in thePTRACKmode.Fixed performance degradation for index-only scans over wide indexes.
Ended support for ALT Linux SPT 6.0 and Windows 7 SP1.
Updated
pg_pathmanmodule to version 1.5.5. As compared to version 1.5.2 provided in the previousPostgres Pro releases, the following enhancements were introduced:Fixed
pg_pathmanupgrade scripts to avoid issues caused by a different the number ofpg_configattributes inpg_pathman1.4 and 1.5 major versions.Improved
pg_pathmanstability:Trying to call
pg_pathmanfunctions when this extension is disabled does not cause server failures anymore; now an error is raised instead.Different partitioning strategies can now be successfully applied to the same table.
Updated
pg_variablesmodule to version 1.2:Added support for array types.
Improved module stability.
Changed empty package handling. An empty package is now removed only after the transaction that emptied it has ended.
(SeeSection F.44.)
E.17.2. Migration to Version 10.7.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.
Sincepg_probackup delivery model changed inPostgres Pro Standard 10.7.1, when upgrading from a lower version on ALT Linux and Debian-based systems, runapt dist-upgrade (orapt-get dist-upgrade) to ensure that all new dependencies are handled correctly. On Windows, you have to run a separatepg_probackup installer to complete the upgrade.
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.