Movatterモバイル変換

Important

The final release ofPostgres 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.

• Optimized the behavior when working with theCOALESCE function. 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 incrash_info output 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 ofSIGILL (illegal instruction) signals. The way of dumping stack files in case of crashes has also been changed for Linux x64. Besides,memory_context has 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 inLISTEN/NOTIFY queue handling, which caused failure to obtain transaction status. Previously,VACUUM FREEZE could advancedatfrozenxid too far forward.

• Fixed an issue where the planner could choose non-optimal execution plans for queries that use theLIKE operator with themchar data type.

• Ended support for Ubuntu 20.04.

• Upgradedaqo to provide the following bugfixes:

  • Fixed the race condition when calling theaqo_cleanup function 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 theEXPLAIN output. 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_probackup to version 2.8.10, which provides the following new features, optimizations, and bug fixes:

  • Added the--wal-tree option for theadd-instance command to store archived WAL files in a tree-like structure. This improves WAL operation performance with large volumes of logs.

  • Added thepostgres-edition field to theshow command output in theJSON format to display DBMS edition information.

  • Improved the--dry-run option 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 thearchive-get command operation. Thepbk_prefetch directory is now created with correct access rights, inheriting permissions fromPGDATA.

  • Fixed false failure of thecheckdb command in the remote mode during concurrentTRUNCATE operations or table drops on standby nodes.

• 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 the1c.tune preset 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 multipleORDER BY clauses.