E.4. Postgres Pro Enterprise 16.3.2 #
Release Date: 2024-07-02
E.4.1. Overview #
This release is based on Postgres Pro Enterprise 16.3.1 and provides the following changes:
Fixed two issues that could occur after upgrading from PostgreSQL or Postgres Pro Standard using pg_upgrade: fixed
xidbase calculation during heap page pruning andxmaxcalculation during page conversion from 32-bit to 64-bit format. These issues didn't result in data loss or corruption but raised PANIC-level errors.Fixed a segmentation fault caused by improper memory management in CFS, which could occur in some corner cases where CFS garbage collector was disabled or a standby server restored WAL records for a long time (e.g. it was lagging far behind).
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.The enable_compound_index_stats configuration parameter was enabled.
The tables involved in the query had multi-column
INCLUDEindexes.
Upgraded pgpro_sfile to version 1.1, which provides two bug fixes:
Fixed an issue with the sf_read function where reading from an offset greater than 8096 bytes would return data from the beginning of the
sfileobject.Fixed copying of
sfilecolumn values in binary format.
Upgraded orafce to version 4.10.3.
Upgraded pg_probackup to version 2.8.2 Enterprise, 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 enabling pg_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.4.2. Migration to Version 16.3.2 #
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.
Important
If you take backups using pg_probackup and you have previously upgraded it to version 2.8.0 Enterprise or 2.8.1 Enterprise, make sure to upgrade it to version 2.8.2 Enterprise 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 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 16.