E.17. Postgres Pro Standard 13.8.1
Release Date: 2022-08-30
E.17.1. Overview
This release is based onPostgreSQL 13.8 andPostgres Pro Standard 13.7.2. All improvements inherited fromPostgreSQL 13.8 are listed inPostgreSQL 13.8 Release Notes. Other major changes and enhancements are as follows:
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.Ended support for Ubuntu 21.10 and added support for Red Hat Enterprise Linux 9 and its derivatives: Rocky Linux 9, Oracle Linux 9, and AlmaLinux 9.
Added theaqo extension for adaptive query optimization toPostgres Pro Standard.
Upgradedmamonsu to version 3.5.1. Notable changes are as follows:
Enabledmamonsu plugins to usepgpro_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 themamonsuSTATEMENTS plugin.
Upgradedpg_probackup to version 2.5.7, which provides the following new features and bugfixes:
Upgradedpgpro_pwr to version 4.0.
Added theoracle_fdw package for Red OS Murom 7.3.
E.17.2. Migration to Version 13.8.1
If you are upgrading fromPostgres Pro Standard based on the samePostgreSQL major version, it is enough to install the new version into your current installation directory.
When upgrading fromPostgres Pro versions 13.2.1 or lower, rebuild indexes containing at least one included column of type for which the collation was defined in the table.
If you are upgrading fromPostgres Pro versions 13.2.2 or lower and takePTRACK backups usingpg_probackup, retake a full backup after upgrade.
To migrate fromPostgreSQL or aPostgres Pro Standard release based on a previousPostgreSQL major version, see the instructions inPostgres Pro Standard 13.1.1 Release Notes.