E.1. Postgres Pro Standard 14.19.1
Release Date: 2025-09-10
E.1.1. Overview
This release is based onPostgreSQL 14.19 andPostgres Pro Standard 14.18.1. All improvements inherited fromPostgreSQL 14.19 are listed inPostgreSQL 14.19 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 ofcrash_info:
Added thecrash_info_timer,crash_info_timer_interval, andcrash_info_query_threshold configuration parameters that allow profiling long queries in
crash_infooutput files.Extended the diagnostic information that thecrash_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.Added support for Debian 13, Red Hat Enterprise Linux 10, Rocky Linux 10, Oracle Linux 10, and AlmaLinux 10.
Ended support for Ubuntu 20.04.
Upgradedaqo to provide the following bugfixes:
Fixed the race condition when calling the
aqo_cleanupfunction from different sessions.Fixed an issue whereaqo learning data was not saved for queries that use materialization.
Upgradedauto_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.Upgradedpg_proaudit to provide the following enhancements:
Upgradedpg_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 wherepg_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.
Fixed the following issues in thepgpro_bindump module:
Fixed potentialpg_probackup3 failure caused by temporary tables during backup validation using thepgpro_bindump module in the PRO mode.
Fixed a memory leak inpg_probackup3 using thepgpro_bindump module for PTRACK operations.
Fixed an issue that could cause infinite looping inpg_probackup3 when using thepgpro_bindump module.
Fixed an issue with multi-timeline backup in the PTRACK mode inpg_probackup3 using thepgpro_bindump module in the PRO mode.
Upgradedpgpro_pwr to version 4.10, which completely redesigns the report and supportsPostgreSQL 18.
Upgradedpgpro_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 thepgpro_tune utility.Upgradedpg_query_state to version 1.2 to add thepg_progress_bar andpg_progress_bar_visual functions that allow monitoring the current progress of query execution.
Upgradedrum 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 14.19.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.
Starting fromPostgres Pro Standard 14.10.1, the privileges ofCREATEROLE are restricted, and modification of other roles requires the role requesting the change to have theADMIN OPTION permission.
When upgrading toPostgres Pro versions starting with 14.8.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 14.1.1 Release Notes.