E.19. Postgres Pro Enterprise 13.7.1
Release Date: 2022-06-14
E.19.1. Overview
This release is based on PostgreSQL 13.7 and Postgres Pro Enterprise 13.6.1. All changes inherited from PostgreSQL 13.6 are listed in PostgreSQL 13.7 Release Notes. As compared with Postgres Pro Enterprise 13.6.1, this version also provides the following changes:
Fixed "PANIC: WAL contains references to invalid pages" failure on a replica when the number of transactions exceeded 2^31 and
full_page_writeswas off.Fixed an issue that could occur when attempting to read a parameter being NULL (including reads when calling
set_config().setting_name,null,is_local)Changed the algorithm of composite type name generation. This fixes an issue in the code of vanilla PostgreSQL, which strictly limits the number of tables with the same long prefix in names.
Added support for Ubuntu 22.04.
Ended support for OSnova 2.0.
Made the pg_freespacemap
pg_freespacefunction display the correct amount of free space on pages for tables in CFS tablespaces. The function is now implemented in C instead of SQL used before.Upgraded pg_probackup to version 2.5.6, which provides the following new features and bugfixes as compared to version 2.5.5:
Added the
--dry-runflag to thecatchupcommand to allow you to estimate the size of data files to be transferred, but make no changes on disk.Changed the level of detail of logging some
catchupmessages for user convenience of log reading.Fixed a bug that prevented correct rereading of a block after a message “File: ... blknum ... have wrong checksum, try again” was issued.
Upgraded PTRACK to version 2.3.0, optimizing PTRACK map loading, which previously in some cases could considerably slow down overall database loading. A substantial speed-up is observed for large-size maps.
Upgraded pgpro_stats to version 1.4, which provides the following new features and bugfixes:
Added
pgpro_stats_vacuum_tablesandpgpro_stats_vacuum_indexesviews, which show statistics about vacuuming tables and indexes, respectively. Functions with the same names, which define these views for any specified database and table/index, are also added and can return statistics about vacuuming all tables/indexes in the specified database too.Fixed a bug in extra shared memory allocation. The size of this memory was calculated with an error, which could cause memory corruption, incorrect computation of statistics or even a server crash.
Fixed an issue that caused a server crash when queries that only differ in constants contained in the query text were sent one after another through the extended query protocol.
Upgraded pgpro_pwr to version 3.9, which provides the following new features and bugfixes:
Added statistics on invalidation messages and on vacuuming tables and indexes to the report.
Optimized retention handling for obsolete dictionary entries in the pgpro_pwr historical repository.
Fixed the type of value in calculating the wait time while taking a sample. This prevents a yet unlikely integer overflow error.
Renamed the vops-specific
unnest()function with conflicting definition tovops_unnest().
E.19.2. Migration to Version 13.7.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 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.