E.2. Postgres Pro Standard 13.16.1
Release Date: 2024-08-14
E.2.1. Overview
This release is based on PostgreSQL 13.16 and Postgres Pro Standard 13.15.2. All improvements inherited from PostgreSQL 13.16 are listed in PostgreSQL 13.16 Release Notes. Other major changes and enhancements are as follows:
Enhanced performance of segment search by implementing a new search strategy, allowing faster detection of the last segment.
Fixed a bug that caused the optimizer to ignore columns from query conditions. Previously, when partially using a composite index, the number of rows could be overestimated, which led to an incorrect plan creation. The bug occurred due to a malfunction of the multi-column statistics elements.
Fixed a bug in
ANALYZEthat could occur because it was impossible to display thepg_statisticsystem catalog. For the fix to work, if your database has indexes withINCLUDEcolumns, after upgrading Postgres Pro, it is recommended to do anotherANALYZEfor these columns.Added support for ALT 11.
Ended support for Ubuntu 23.04.
Upgraded the mchar extension to fix a bug that caused the
mcharandmvarchardata types to ignore control characters during string comparison.Upgraded pg_probackup to version 2.8.3, which fixes backup validation for databases containing an OID larger than 109. Previously, the validation status could be displayed incorrectly in such cases.
Upgraded pg_filedump to version 17.0, which provides optimizations and bug fixes. In particular, contents of meta pages for GIN and SP-GiST indexes are now displayed correctly, and an issue of lacking memory for encoding and decompression is resolved.
Fixed incorrect behavior of pg_wait_sampling when used with the extended query protocol.
E.2.2. Migration to Version 13.16.1
If you are upgrading from Postgres Pro Standard based on the same PostgreSQL major version, it is enough to install the new version into your current installation directory.
If you take backups using pg_probackup and you have previously upgraded it to version 2.8.0 or 2.8.1, make sure to upgrade it to version 2.8.2 or higher and retake a full backup after upgrade, since backups taken using those versions might be corrupted. If you suspect that your backups taken with versions 2.8.0 or 2.8.1 may be corrupted, you can validate them using version 2.8.2.
When upgrading from Postgres 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 from Postgres Pro versions 13.2.2 or lower and take PTRACK backups using pg_probackup, retake a full backup after upgrade.
When upgrading to Postgres Pro versions starting with 13.11.1, make sure to upgrade pg_probackup to version 2.6.3 or higher since lower versions are incompatible with these Postgres Pro versions.
To migrate from PostgreSQL or a Postgres Pro Standard release based on a previous PostgreSQL major version, see the instructions in Postgres Pro Standard 13.1.1 Release Notes.