E.1. Postgres Pro Standard 13.22.1
Release Date: 2025-09-08
E.1.1. Overview
Important
The final release of Postgres Pro 13 is scheduled for November 2025. No further updates (including CVE patches and bug fixes) will be provided for this version as of December 1, 2025. If you are using version 13, we recommend that you upgrade to the latest major version no later than November 30, 2025.
This release is based on PostgreSQL 13.22 and Postgres Pro Standard 13.21.1. All improvements inherited from PostgreSQL 13.22 are listed in PostgreSQL 13.22 Release Notes. Other major changes and enhancements are as follows:
Optimized the behavior when working with the
COALESCEfunction. Now this function is replaced with one of its arguments if all other arguments were evaluated tonull. This allows improving the selectivity of query clauses and producing better execution plans.Introduced the following changes to the implementation of crash_info:
Added the crash_info_timer, crash_info_timer_interval, and crash_info_query_threshold configuration parameters that allow profiling long queries in
crash_infooutput files.Extended the diagnostic information that the crash_info_dump configuration parameter can specify to write in case of a backend crash. By default, now the general information on the signal is dumped and for Linux x64, also the information on the processor state and bytes near RIP (return instruction pointer). All this ensures better diagnostics, in particular, in case of
SIGILL(illegal instruction) signals. The way of dumping stack files in case of crashes has also been changed for Linux x64. Besides,memory_contexthas been removed from the default list of sources to be dumped in order to avoid failures that could occur when writing the diagnostic information.
Fixed an issue in
LISTEN/NOTIFYqueue handling, which caused failure to obtain transaction status. Previously,VACUUM FREEZEcould advancedatfrozenxidtoo far forward.Fixed an issue where the planner could choose non-optimal execution plans for queries that use the
LIKEoperator with themchardata type.Ended support for Ubuntu 20.04.
Upgraded aqo to provide the following bugfixes:
Fixed the race condition when calling the
aqo_cleanupfunction from different sessions.Fixed an issue where aqo learning data was not saved for queries that use materialization.
Upgraded auto_explain to move the planning time of a query in the output to a separate line under the planner tree, as in the
EXPLAINoutput. With the former location of the planning time in the output, pgbadger could not recognize the information on a query and therefore did not include it in the report.Upgraded pg_probackup to version 2.8.10, which provides the following new features, optimizations, and bug fixes:
Added the
--wal-treeoption for theadd-instancecommand to store archived WAL files in a tree-like structure. This improves WAL operation performance with large volumes of logs.Added the
postgres-editionfield to theshowcommand output in theJSONformat to display DBMS edition information.Improved the
--dry-runoption operation during tablespace recovery. The operation estimation and plan output are now more precise.Fixed an issue related to the retention window calculation. The time value is now taken from the host where pg_probackup is running. The retention window is now calculated correctly even with the timezone differences between the servers.
Fixed a problem with the
archive-getcommand operation. Thepbk_prefetchdirectory is now created with correct access rights, inheriting permissions fromPGDATA.Fixed false failure of the
checkdbcommand in the remote mode during concurrentTRUNCATEoperations or table drops on standby nodes.
Upgraded pgpro_pwr to version 4.10, which completely redesigns the report and supports PostgreSQL 18.
Upgraded pgpro_stats to fix a segmentation fault that could occur when defining custom metrics. The error originated from a memory allocation issue, which was fixed.
Fixed an issue with incorrect configuration parameter values specified when using the
1c.tunepreset of the pgpro_tune utility.Upgraded pg_query_state to version 1.2 to add the pg_progress_bar and pg_progress_bar_visual functions that allow monitoring the current progress of query execution.
Upgraded rum to provide the following bugfixes:
Fixed a segmentation fault caused by invalid memory access when a buffer pointer was used after the underlying buffer was modified by another thread.
Fixed an index scan infinite loop when using multiple
ORDER BYclauses.
E.1.2. Migration to Version 13.22.1
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.
ABI versions may change between minor releases of Postgres Pro. If this is the case, and you see the ABI mismatch error when trying to run your extension, make sure to install a new version of the extension supplied with a new release of Postgres Pro, or recompile your third-party extension to be able to use it with the current version of Postgres Pro.
If you take backups using pg_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.
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.