E.8. Postgres Pro Standard 13.14.1
Release Date: 2024-02-14
E.8.1. Overview
This release is based onPostgreSQL 13.14 andPostgres Pro Standard 13.13.1. All improvements inherited fromPostgreSQL 13.14 are listed inPostgreSQL 13.14 Release Notes. Other major changes and enhancements are as follows:
Added configuration parameters to enable getting information on crashes of a backend. Thecrash_info parameter turns on this functionality, whilecrash_info_dump andcrash_info_location specify the contents and location of crash information files, respectively.
Added
-m
,-o
, and-x
options toinitdb for testing database upgrades with custom initial xid, multixid and multixid offset values. These options were previously available only inPostgres Pro Enterprise.Optimized memory consumption during selectivity estimation for each array element as compared to vanillaPostgreSQL.
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 aPostgres Pro server on Debian-based systems included in a domain with the
postgres
user.Fixed the output ofpg-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.
Upgradedorafce to version 4.9.1.
Upgradedpg_filedump to version 16.1.
Upgradedpg_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.
Upgradedpg_repack to version 1.5.0.
Upgradedpg_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.
Upgradedpgpro_stats to version 1.7, which provides optimizations and bug fixes:
Similarly to apg_stat_statements fix, changedpgpro_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
andpgpro_stats_totals
functions. Now a newer version of thepgpro_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.
Upgradedpgpro_pwr to version 4.4, which supportspgpro_stats 1.7, as well as adds more interactive features and substring-based filtering to the report.
E.8.2. Migration to Version 13.14.1
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.
When upgrading fromPostgres 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 fromPostgres Pro versions 13.2.2 or lower and takePTRACK backups usingpg_probackup, retake a full backup after upgrade.
When upgrading toPostgres Pro versions starting with 13.11.1, make sure to upgradepg_probackup to version 2.6.3 or higher since lower versions are incompatible with thesePostgres Pro versions.
To migrate fromPostgreSQL or aPostgres Pro Standard release based on a previousPostgreSQL major version, see the instructions inPostgres Pro Standard 13.1.1 Release Notes.