Improved performance by introducing a more efficient synchronization primitive instead of previously used spinlocks for a shared invalidation message queue, which allows avoiding a bottleneck. This may be useful for 1C.

Improved performance by suppressing catalog cache invalidation messages for DDL operations on temporary tables and for analyzing these tables. This is useful for 1C.

Improved performance by avoiding invalidation of the pg_internal.init file when analyzing catalog tables, particularly when statistics for these tables change frequently. This may be useful for 1C.

Improved performance by reducing the number of lock requests for the pg_attribute and pg_statistic tables for queries with a large number of relations that are not present in the system cache. This may be useful for some usage scenarios with 1C.

Improved performance of non-transactional truncate operations on temporary tables and fast truncate operations. This is useful for 1C.

Added the skip_temp_rel_lock=on setting to the 1c.tune preset of the pgpro_tune utility to optimize fasttrun performance.

Improved performance by adding a possibility to skip locking for indexes on temporary relations, which can be enabled using the skip_temp_rel_lock parameter. This is useful for 1C.

Updated CREATE DATABASE, createdb, and initdb to display an information message when the value of lc_collate is used as the default for icu_locale or --icu-locale.

Optimized the behavior when working with the COALESCE function. Now this function is replaced with one of its arguments if all other arguments were evaluated to null. This allows improving the selectivity of query clauses and producing better execution plans.

Introduced the following changes to the implementation of crash_info:

Added a possibility for the optimizer to use memoize nodes for parameterized ANTI JOINs when the enable_extra_transformations parameter is set to on.

Implemented the following enhancements and bug fixes for CFS:

Fixed excessive memory usage by the disabled built-in connection pooler.

Fixed an issue with autonomous transactions, which caused a failure to release resources, leading to accumulation of cached plan references.

Fixed page image inconsistency during heap insert on an empty page. Previously, this could result in incorrect page contents on standby servers.

Fixed an issue with page conversion from 32-bit to 64-bit format after migration to Postgres Pro Enterprise using pg_upgrade. When a page was converted only in memory, without writing it to disk, and autovacuum removed corresponding pg_xact segments at the same time, transaction status in tuples was lost, leading to errors on access.

Fixed a possible race condition in the walreceiver process.

Fixed an issue in LISTEN/NOTIFY queue handling, which caused failure to obtain transaction status. Previously, VACUUM FREEZE could advance datfrozenxid too far forward.

Fixed an issue where the planner could choose non-optimal execution plans for queries that use the LIKE operator with the mchar data 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.

Upgraded aqo to provide the following bugfixes:

Upgraded auto_explain to move the planning time of a query in the output to a separate line under the planner tree, as in the EXPLAIN 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.

Fixed an issue where fasttrun could fail to fully truncate temporary tables if the cached segment count was smaller than the actual number of file segments on disk, leaving disk space occupied even though the table appeared empty.

Upgraded multimaster to provide the following enhancements and bug fixes:

Implemented the ability to configure LDAP authentication for pgbouncer by means of PAM (Pluggable Authentication Modules). For more information, see LDAP Authentication Configuration for pgbouncer.

Updated the pg_freespacemap module to include the pg_freespace_relation_logical_blocks function for computing the disk space used by relation forks. This function works with both compressed and uncompressed tables.

Fixed a memory allocation issue in pg_prewarm, which could previously produce errors like “invalid memory alloc request size” when shared_buffers was set to a huge value.

Upgraded pg_proaudit to provide the following enhancements:

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

Fixed the following issues in the pgpro_bindump module:

Updated the pgpro_datactl utility to include the following new features:

Upgraded pgpro_multiplan to version 1.3, which provides the following enhancements, changes, and bug fixes:

Upgraded pgpro_pwr to version 4.10, which completely redesigns the report and supports PostgreSQL 18.

Upgraded pgpro_scheduler to version 2.12, which provides the following bug fixes and improvements:

Upgraded pgpro_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.tune preset of the pgpro_tune utility.

Upgraded pg_query_state to version 1.2 to add the pg_progress_bar and pg_progress_bar_visual functions that allow monitoring the current progress of query execution.

Added the --enable-large-mem-buffers option to the pg_restore to allow restoring a database that does not contain large bytea values and records with several text values as a non-superuser.

Fixed an issue in postgres_fdw, which could cause UPDATE and DELETE queries with a RETURNING clause to fail with “out of memory for query result” errors. Now RETURNING results are processed row-by-row.

Upgraded rum to provide the following bugfixes:

Fixed a PANIC-level failure in sr_plan, which could occur if the standby had a different sr_plan version than the primary.