Request a Demo
E.1. Postgres Pro Standard 13.23.1
Prev UpAppendix E. Release NotesHome Next

E.1. Postgres Pro Standard 13.23.1

E.1.1. Overview
E.1.2. Migration to Version 13.23.1

Release Date: 2025-12-01

E.1.1. Overview

This is expected to be the last Postgres Pro Standard release in the 13 series. Users are encouraged to update to a newer Postgres Pro Standard major version soon.

This release is based on PostgreSQL 13.23 and Postgres Pro Standard 13.22.1. All improvements inherited from PostgreSQL 13.23 are listed in PostgreSQL 13.23 Release Notes. Other major changes and enhancements are as follows:

  • Improved the search mechanism for matching mchar and mvarchar strings using the LIKE operator. Optimized case-insensitive comparison results in significant speed increase. This may be useful for 1C.

  • Improved performance of getting information on crashes of a backend by optimizing utility functions and commands.

  • Added the enable_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_TUNE environment variable used by initdb.

  • Added the pg_trgm_mchar extension, which allows fast trigram-based search for similar mchar and mvarchar strings. This extension also provides support of GIN indexes for mchar and mvarchar types. This may be useful for 1C.

  • Upgraded pgbouncer to version 1.25.0.

  • Upgraded pg_filedump to version 18.0.

  • Upgraded pg_probackup to version 2.8.11, which provides the following new features, optimizations, and bug fixes:

    • Added support for Postgres Pro Standard 18.

    • Made the host from which a backup was taken to be saved in backup.control and displayed in the show command output.

    • Improved the behavior during restore from read-only media, including more informative warning messages.

    • For archive-push and archive-get operations in the remote mode, made SIGQUIT 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 --force flag, the tablespace contents are no longer overwritten.

    • Fixed a problem with the backup command holding the replication slot after successful completion.

    • Fixed the identifier conflict for the --wal-tree option by adding a uniqueness test.

    • Fixed the order of displaying the calculated and expected checksum values in the warning message.

  • Upgraded pgpro_controldata to version 18.1.0.

  • Upgraded pgpro_pwr to version 4.12, which provides optimizations and bug fixes. Notable changes are as follows:

    • Improved take_sample time tracking.

    • Added support of pgpro_stats 1.10.

    • Added a possibility to exclude server connection strings from dumps.

    • Added statistics on restartpoints to the reports when it is available.

  • Upgraded pgpro_stats to version 1.10 to provide the following enhancements and bug fixes:

    • Added new statistics to pgpro_stats_statements and pgpro_stats_totals views. These statistics were added to pg_stats_statements in Postgres Pro 18. Related functions are updated accordingly.

    • Added the new pgpro_stats_statements_filtered function to filter statistics similar to those provided in the pgpro_stats_statements view by one or several fields: userid, dbid, queryid, and planid. Calling this function is faster than querying the pgpro_stats_statements view with appropriate values of these fields.

    • Improved the behavior of pgpro_stats similarly to pg_stat_statements. The changes are:

      • Allow the parameterization of SET values. This reduces the bloat caused by SET statements with differing constants.

      • Allow the parameterization of constant lists.

    • Fixed an issue that could occur when in pgpro_stats custom metrics were changed on the fly. Now any change to custom metrics requires a server restart.

  • Upgraded rum to fix a bug with the module upgrade that was caused by an incorrect variable specified in its makefile.

  • Disabled online_analyze. This module is not recommended for use with modern versions of 1C. However, it can be enabled if needed.

E.1.2. Migration to Version 13.23.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.

Prev Up Next
Appendix E. Release Notes Home E.2. Postgres Pro Standard 13.22.1
epub pdf