E.17. Postgres Pro Enterprise 13.8.1
Release Date: 2022-09-08
E.17.1. Overview
This release is based on PostgreSQL 13.8 and Postgres Pro Enterprise 13.7.1. All changes inherited from PostgreSQL 13.8 are listed in PostgreSQL 13.8 Release Notes. As compared with Postgres Pro Enterprise 13.7.1, this version also provides the following changes:
Fixed various issues in pg_upgrade. In particular, now free space maps and visibility maps are handled correctly during the upgrade.
Fixed a bug in the logic of epoch shifting, which didn't take into account the
XMAX_INVALIDhint bit of the tuple. Previously, it could lead to a sudden increase of the current transaction ID.Resolved an issue that caused an error “duplicate key value violates unique constraint” when indexing a database in multiple threads. Now the chosen name of a type being created for the index gets locked to avoid choosing the same name in a parallel process.
Resolved an issue in the planner's use of the compound indexes statistics: the optimizer reduced the cost prediction accuracy for a query plan if in the
WHEREclause of the query, values of different types were compared (for example:integerandnumeric,textandname). Sometimes, for certain combinations of the compared types and values, the issue could cause a server crash.Added support for Red Hat Enterprise Linux 9 and its derivatives: Rocky Linux 9, Oracle Linux 9, and AlmaLinux 9.
Upgraded mamonsu to version 3.5.1. Notable changes are as follows:
Enabled mamonsu plugins to use pgpro_stats to collect statistics.
Resolved the security issue of exposing passwords through the configuration file. Only
mamonsuuser can accessagent.confnow.Fixed metrics computation that caused “float division by zero” errors in the mamonsu STATEMENTS plugin.
Upgraded pg_probackup to version 2.5.7, which provides the following new features and bugfixes:
Enabled output of logs in the JSON format by adding new logging options.
Added an option to explicitly specify the directory where the
restorecommand should restore WAL records.Changed the level of detail of logging some messages of pg_probackup commands to add user convenience to reading logs.
Fixed pg_probackup hanging that could occur when the
ControlMasteroption was specified in the SSHconfigfile. Now the value ofControlMasteris explicitly set to “no”.
Upgraded pgpro_pwr to version 4.0.
Added the oracle_fdw package for Red OS Murom 7.3.
E.17.2. Migration to Version 13.8.1
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.
If you are migrating to the current major version of Postgres Pro Enterprise using pg_upgrade, and you want to keep the existing visibility map representation in pageinspect, you should run the VACUUM command before the upgrade.
If you have previously migrated to Postgres Pro Enterprise 13.3.1 or lower, you must run the REINDEX command to rebuild GIN indexes.
If you are upgrading from Postgres Pro Enterprise versions 13.2.2 or lower and take PTRACK backups using pg_probackup, retake a full backup after upgrade.
If you have an installation of Postgres Pro Enterprise 13.2.1 that contains compressed tablespaces created without explicitly specifying the pglz algorithm, perform an upgrade as follows. Before upgrading, make a complete dump using pg_dumpall. Upgrade Postgres Pro Enterprise, re-create your database cluster, and restore the dump. Then you can create compressed tablespaces in the same way as before.
If you have already upgraded your installation with CFS tablespaces from Postgres Pro Enterprise 13.2.1, and you cannot access the compressed data, call the support team.
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 13.