E.1. Postgres Pro Standard 13.20.1
Release Date: 2025-02-27
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 version no later than November 30, 2025.
This release is based on PostgreSQL 13.20 and Postgres Pro Standard 13.18.1. All improvements inherited from PostgreSQL 13.20 are listed in PostgreSQL 13.20 Release Notes. Other major changes and enhancements are as follows:
Fixed an issue where
crash_infocould fail to write diagnostic files when handling a stack overflow. Previously, the signal handler ran on the same stack that had overflowed, which could prevent it from executing due to lack of available stack space. Now the handler runs on an alternate signal stack.Fixed a memory context issue, which could previously cause emitting garbage in logs instead of the host and port details when disconnecting from the remote server.
Fixed an issue that could occur when a custom scan was used, which could cause an incorrect state of the query plan and could result in an error when pgpro_stats was involved.
Added details, like current working directory, the
PGDATAdirectory, etc., tocrash_infooutput files.Optimized fasttrun to skip unnecessary truncate operations on empty temporary relations.
Upgraded mamonsu to version 3.5.11 to provide support for pgpro_stats version 1.8.
Upgraded pgbadger to version 13.0.
Upgraded pgbouncer to version 1.24.0.
Upgraded pg_portal_modify to version 0.3.5.
Upgraded pg_probackup to version 2.8.7, which provides the following optimizations and bug fixes:
Fixed an issue of the multi-threaded file copying technique that prevents repeated copying of one file. This issue could previously stop the backup creation under high load on the server.
Reduced the log level for “checking WAL file name” messages that are issued when the
showwith the--archiveoption is executed fromINFOtoVERBOSE.Updated the
add-instancecommand logic to make the-Doption that specifies the path to the catalog mandatory.add-instanceno longer relies on thePGDATAenvironment variable for the catalog location, but requires explicitly specifying the path to the catalog as the command option.
Upgraded pgpro_pwr to version 4.8, which provides new features and bug fixes. Notable changes are as follows:
Added tracking of extension versions installed in the cluster through a new report section.
Added a possibility to hide data for certain databases in the report. To this end, a new parameter that accepts an array of databases to be excluded was added to report generation functions.
Upgraded pgpro_stats to version 1.8.1, which provides the following bug fixes and improvements:
Fixed an issue in that could occur during session tracing and cause errors “could not write file ""pg_stat/pgpro_stats_filters.trace.tmp"": No such file or directory”. Concurrent writing from different sessions to a trace file is fixed now, so processes can write to the trace file in parallel without collisions.
Changed the format of the statistics dump file and the corresponding save/load routines.
Implemented an optimization that lowers the locking time in some cases when copying metrics from the local memory to the shared memory.
Aligned the names of the
explain_*filter attributes of the session tracer with the names of session-tracing configuration parameters.Implemented turning off the session tracer functionality when no session-tracing filters are specified.
Upgraded pg_variables. The
DISCARD ALLcommand now discards all packages and variables in pg_variables.Upgraded the rum module to update an error message for an error that can occur in the case when a
SELECTquery usesORDER BY.
E.1.2. Migration to Version 13.20.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.