E.1. Postgres Pro Standard 13.23.1
Release Date: 2025-12-01
E.1.1. Overview
This is expected to be the lastPostgres Pro Standard release in the 13 series. Users are encouraged to update to a newerPostgres Pro Standard major version soon.
This release is based onPostgreSQL 13.23 andPostgres Pro Standard 13.22.1. All improvements inherited fromPostgreSQL 13.23 are listed inPostgreSQL 13.23 Release Notes. Other major changes and enhancements are as follows:
Improved the search mechanism for matching
mcharandmvarcharstrings using theLIKEoperator. Optimized case-insensitive comparison results in significant speed increase. This may be useful for1C.Improved performance ofgetting information on crashes of a backend by optimizing utility functions and commands.
Added theenable_sorted_merge_join configuration parameter that enables or disables the query planner's use of merge joins in plans with sorting.
Added new values of the
PGPRO_TUNEenvironment variable used byinitdb.Added thepg_trgm_mchar extension, which allows fast trigram-based search for similar
mcharandmvarcharstrings. This extension also provides support of GIN indexes formcharandmvarchartypes. This may be useful for1C.Upgradedpgbouncer to version 1.25.0.
Upgradedpg_filedump to version 18.0.
Upgradedpg_probackup to version 2.8.11, which provides the following new features, optimizations, and bug fixes:
Added support forPostgres Pro Standard 18.
Made the host from which a backup was taken to be saved in
backup.controland displayed in theshowcommand output.Improved the behavior during restore from read-only media, including more informative warning messages.
For
archive-pushandarchive-getoperations in the remote mode, madeSIGQUIT signals to be ignored to prevent core dumps of helper programs when the server stops.Fixed handling of external tablespaces during incremental restore. When using the
--forceflag, the tablespace contents are no longer overwritten.Fixed a problem with the
backupcommand holding the replication slot after successful completion.Fixed the identifier conflict for the
--wal-treeoption by adding a uniqueness test.Fixed the order of displaying the calculated and expected checksum values in the warning message.
Upgradedpgpro_controldata to version 18.1.0.
Upgradedpgpro_pwr to version 4.12, which provides optimizations and bug fixes. Notable changes are as follows:
Improved
take_sampletime tracking.Added support ofpgpro_stats 1.10.
Added a possibility to exclude server connection strings from dumps.
Added statistics on restartpoints to the reports when it is available.
Upgradedpgpro_stats to version 1.10 to provide the following enhancements and bug fixes:
Added new statistics to
pgpro_stats_statementsandpgpro_stats_totalsviews. These statistics were added topg_stats_statements inPostgres Pro 18. Related functions are updated accordingly.Added the new
pgpro_stats_statements_filteredfunction to filter statistics similar to those provided in thepgpro_stats_statementsview by one or several fields:userid,dbid,queryid, andplanid. Calling this function is faster than querying thepgpro_stats_statementsview with appropriate values of these fields.Improved the behavior ofpgpro_stats similarly topg_stat_statements. The changes are:
Allow the parameterization ofSET values. This reduces the bloat caused by
SETstatements with differing constants.Allow the parameterization of constant lists.
Fixed an issue that could occur when inpgpro_stats custom metrics were changed on the fly. Now any change to custom metrics requires a server restart.
Upgradedrum to fix a bug with the module upgrade that was caused by an incorrect variable specified in its makefile.
Disabledonline_analyze. This module is not recommended for use with modern versions of1C. However, it can be enabled if needed.
E.1.2. Migration to Version 13.23.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.
ABI versions may change between minor releases ofPostgres Pro. If this is the case, and you see theABI mismatch error when trying to run your extension, make sure to install a new version of the extension supplied with a new release ofPostgres Pro, or recompile your third-party extension to be able to use it with the current version ofPostgres Pro.
If you take backups usingpg_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 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.