E.1. Postgres Pro Standard 13.21.1
Release Date: 2025-05-26
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.21 and Postgres Pro Standard 13.20.1. All improvements inherited from PostgreSQL 13.21 are listed in PostgreSQL 13.21 Release Notes. Other major changes and enhancements are as follows:
Added the enable_alternative_sorting_cost_model configuration parameter, which allows you to enable or disable the query planner's use of alternative model for estimating the cost of tuple sorting.
Introduced the following changes to the implementation of crash_info:
Added handling of
SIGILL
signals tocrash_info
processing.Added details, like process start time and query text at planning, to
crash_info
output files.Fixed incorrect function names in the first 2-3 lines of
crash_info
backtrace stacks.Fixed possible data truncation at the end of SQL query dump files. Previously, a buffer overflow during SQL query dumping could result in incomplete writes, causing truncated data at the end of files produced by
crash_info
.Fixed handling of crash information signals (sent using the kill command) by backends. Previously, the first signal would flush
crash_info
information to the log, but the process would continue running without producing a core dump, even if configured, and only the second signal would terminate the backend and generate the core dump as expected.
Fixed an issue with missing statistics about vacuuming when multiple index vacuum workers are used.
Added the daterange_inclusive extension, which allows you to include the upper bound of a time range in output.
Added the new utility pgpro_tune for automatic tuning of Postgres Pro configuration parameters for all operating systems, except for Windows.
Added a new
PGPRO_TUNE
environment variable to initdb, which specifies whether to use pgpro_tune without modifying command-line options directly.Removed the
--tune
option frompg-setup
. Use the new pgpro_tune utility instead.Upgraded oracle_fdw to provide the following enhancements and bug fixes:
Increased line size for EXPLAIN output as some Oracle catalog queries have long filter conditions. The line size was increased to the value of 3000.
Fixed a crash with column options on non-existing columns. If the Oracle table has fewer columns than the Postgres Pro and one of these extra columns has a column option set, oracle_fdw would write past the end of an array, leading to memory corruption and crashes. Now options for such columns are ignored.
Upgraded pg_probackup to version 2.8.9, which provides the following new features, optimizations, and bug fixes:
Added the
maintain
command to resolve issues that can occur during a forced backup termination.Added the
--lock-lifetime
option that sets the timeout for locks. This option is useful for computational environments with a slow network.Stabilized retaining the initial permissions for directories when running the
init
command.Stabilized the
checkdb
command on a remote host.Improved the stability of the point-in-time recovery (PITR) with validation.
Fixed an incorrect behavior that could occur when launching the wait for a WAL streaming thread in the ARCHIVE WAL delivery mode.
Upgraded pgpro_pwr to version 4.9, which mainly provides optimizations and bug fixes. Notable changes are as follows:
Added support for pgpro_stats 1.9.
Added a possibility to define the mode of collecting relation sizes globally through the
pgpro_pwr.relsize_collect_mode
extension parameter or for a server through theset_server_size_sampling
function parameter.Enabled fine-tuning the server statistics collection by calling the
set_server_setting
function. It allows you to define which statistics should be collected.Added a preview of storage parameters for tables and indexes in the “Schema object statistics” report section.
Upgraded pgpro_stats to version 1.9, which provides the following bug fixes and improvements:
Enhanced session tracing to provide more information. Specifically, the new
time_info
filter attribute controls inclusion of additional information in the session-tracing output, and thepgpro_stats.trace_query_text_size
configuration parameter can limit the size of the query in the session-tracing output.Aligned the names of the
explain_*
filter attributes of the session tracer with the names of session-tracing configuration parameters.Changed the format of the statistics dump file and the corresponding save/load routines.
Implemented turning off the session tracer functionality when no session-tracing filters are specified.
Prohibited inclusion of both pgpro_stats and pg_stat_statements in the list of
shared_preload_libraries
. If both are included, the database server will not start.
Upgraded the pg_wait_sampling extension to provide the following bug fixes:
Fixed an issue where GUC variables could be overridden when using parallel workers.
Fixed an issue with malformed samples caused by a race condition when
pg_wait_sampling.sample_cpu
is disabled.
E.1.2. Migration to Version 13.21.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.