E.5. Postgres Pro Standard 16.3.2#
Release Date: 2024-06-27
E.5.1. Overview#
This release is based onPostgres Pro Standard 16.3.1 and provides the following changes:
Fixed a bug in the backend composite type cache management. This bug could result in a segmentation fault or produce errors like“ERROR: record type has not been registered” during the process of selectivity estimation in query planning under the following conditions:
The query contained at least one
JOINoperator.Theenable_compound_index_stats configuration parameter was enabled.
The tables involved in the query had multi-column
INCLUDEindexes.
Upgradedorafce to version 4.10.3.
Upgradedpg_probackup to version 2.8.2, which provides the following bug fixes:
Fixed an OID parsing issue where databases and tablespaces with relfilenodes greater than a billion were not included in backups.
Fixed an issue in enablingpg_probackup logging with the
--log-level-fileparameter, where the parameter value was written to the configuration file, but no directory for log files was created.
E.5.2. Migration to Version 16.3.2#
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.
Important
If you take backups usingpg_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.
To migrate fromPostgreSQL or aPostgres Pro Standard release based on a previousPostgreSQL major version, see the instructions inPostgres Pro Standard 16.0.1 Release Notes.