E.16. Postgres Pro Standard 10.9.1
Release Date: 2019-06-26
E.16.1. Overview
This release is based on PostgreSQL 10.9 and Postgres Pro Standard 10.7.1. All changes inherited from PostgreSQL 10.9 are listed in PostgreSQL 10.9 Release Notes. Other major changes and enhancements are as follows:
Added support for Rosa Enterprise Linux Server 7 and ROSA COBALT 7 (server edition). The previous versions of these operating systems are no longer supported.
Added support for SUSE Linux Enterprise Server 12 SP3 and SUSE Linux Enterprise Server 15.
Added support for Ubuntu 19.04. Ubuntu 14.04 is no longer supported.
Added support for AlterOS 7.5.
On Windows systems, fixed an issue with updating temporary files for statistics if they are currently in use.
Updated
pg_probackupmodule to version 2.1.3. As compared with version 2.0.26, it offers the following major improvements:Backup and restore of a remote Postgres Pro instance via SSH.
Merging incremental backups with their expired parent backups to satisfy retention policy.
Backing up files and directories located outside of Postgres Pro data directory, such as configuration or log files.
The
checkdbcommand for validating all data files in the Postgres Pro instance and logical verification of indexes using amcheck.
For a full list of changes, see pg_probackup Wiki.
Updated
pg_pathmanmodule to version 1.5.8. As compared to version 1.5.5 provided in the previous Postgres Pro releases, the following enhancements were introduced:Fixed handling of tables with multilevel partitioning. Previously,
SELECT FOR SHAREandSELECT FOR UPDATEcommands for such tables could return the following error:ERROR: variable not found in subplan target lists.Enhanced
pg_pathmanstability.
E.16.2. Migration to Version 10.9.1
If you are upgrading from a Postgres Pro Standard version based on the same PostgreSQL major release, it is enough to install the new version into your current installation directory.
Since pg_probackup delivery model changed in Postgres Pro Standard 10.7.1, when upgrading from a lower version on ALT Linux and Debian-based systems, run apt dist-upgrade (or apt-get dist-upgrade) to ensure that all new dependencies are handled correctly. On Windows, you have to run a separate pg_probackup installer to complete the upgrade.
When upgrading from version 10.3.2 or lower, you must call the REINDEX command for indexes that used mchar or mvarchar types. Besides, if you have been using pg_repack on Debian-based systems, you have to reinstall its package manually when upgrading to this version since its package got renamed to pg-repack-std-10.
To migrate from PostgreSQL or a Postgres Pro Standard release based on a previous PostgreSQL major version, see the instructions in Postgres 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.