Release Date: 2024-02-14
This release is based on PostgreSQL 13.14 and Postgres Pro Standard 13.13.1. All improvements inherited from PostgreSQL 13.14 are listed in PostgreSQL 13.14 Release Notes. Other major changes and enhancements are as follows:
Added configuration parameters to enable getting information on crashes of a backend. The crash_info parameter turns on this functionality, while crash_info_dump and crash_info_location specify the contents and location of crash information files, respectively.
Added -m, -o, and -x
options to initdb for testing database upgrades
with custom initial xid, multixid and multixid offset values. These
options were previously available only in
Postgres Pro Enterprise.
Optimized memory consumption during selectivity estimation for each array element as compared to vanilla PostgreSQL.
Fixed the race condition between the autovacuum worker and backend processes when clearing orphaned tables, which could manifest itself in “cache lookup failed for relation” errors. Now autovacuum locks the namespaces when clearing orphaned tables.
Fixed an issue that could occur during installation of a
Postgres Pro server on Debian-based systems
included in a domain with the postgres user.
Fixed the output of pg-setup
, which erroneously
displayed the locale from the LANG environment variable
at cluster initialization. Now the message about locale is not
displayed at this stage.
Ended support for Rosa Enterprise Linux Server 7.
Ended support for ROSA COBALT (server edition) based on Rosa platform 7.
Upgraded orafce to version 4.9.1.
Upgraded pg_filedump to version 16.1.
Upgraded pg_probackup to version 2.7.2, which provides optimizations and bug fixes:
Fixed an issue that occurred during an incremental backup when a table that was not yet copied got removed from CFS.
Fixed the order of processing WAL files by the
archive-push command when the number of WAL
files exceeds the specified --batch-size.
Fixed an error “WAL segment is absent” that could occur when the size of a WAL record being logged exceeded the size of a WAL segment.
Upgraded pg_repack to version 1.5.0.
Upgraded pg_variables, which now provides iterator functionality for any collections, as well as functions to work with general collection variables. These functions allow accessing collection elements by a key that can have either integer or text type. These enhancements facilitate migration of Oracle code that processes collections.
Upgraded pgpro_stats to version 1.7, which provides optimizations and bug fixes:
Similarly to a pg_stat_statements fix, changed pgpro_stats to read its “query texts” file in units of at most 1GB. Such large query text files are very unusual, but if they do occur, the previous coding would fail on Windows 64 (which rejects individual read requests of more than 2GB).
Implemented backward compatibility of
pgpro_stats_statements and
pgpro_stats_totals functions. Now a newer
version of the pgpro_stats shared
library can be safely used with old declarations of SQL functions.
Previously such cases caused a server crash.
Fixed an issue that prevented output of database vacuuming
statistics in the
pgpro_stats_vacuum_database
view.
Upgraded pgpro_pwr to version 4.4, which supports pgpro_stats 1.7, as well as adds more interactive features and substring-based filtering to the report.
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.
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.