Release date: 2019-07-08
This release is based on PostgreSQL 10.9 and Postgres Pro Enterprise 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 Astra Linux Orel 2.12.
Added support for AlterOS 7.5.
Reduced memory consumption for the following cases:
converting table data to JSON format using the row_to_json function
using PL/pgSQL CASE operator with multiple conditions
Updated pg_probackup module 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 checkdb command 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_pathman module 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 SHARE and
SELECT FOR UPDATE commands for such tables
could return the following error:
ERROR: variable not found in subplan target lists.
Enhanced pg_pathman stability.
If you are upgrading from a Postgres Pro Enterprise release based on the same PostgreSQL major version, it is enough to install the new version into your current installation directory.
When upgrading from versions 10.3.3 or lower, you must execute the REINDEX
command for GiST and SP-GiST indexes, as well as indexes that use
mchar or mvarchar types.
To migrate from PostgreSQL,
Postgres Pro Standard, or a
Postgres Pro Enterprise release based on
a previous PostgreSQL major version, see the instructions
in Postgres Pro Enterprise 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 collation provider for the migrated database.