Added the cfs_compression configuration parameter that allows you to temporary disable CFS compression. It speeds up the migration of large compressed tables.

Fixed an issue with CFS failing to compress relation files where OID exceeds INT32_MAX. The issue occurred when moving an existing table to a CFS tablespace.

Fixed an issue where the leader was lost after non-incremental upgrade of a BiHA cluster from Postgres Pro Enterprise 16.8 or lower to 16.10.

Fixed a bug that occurred when the MIN value of the synchronous_standby_names configuration parameter was higher than 0 and the current number of standbys was higher than the num_sync value. This could cause hanging of transactions in case of replication hanging.

Fixed a bug where biha.add_to_ssn, biha.remove_from_ssn, and biha.set_ssn functions modified the list of synchronous standbys of the synchronous_standby_names parameter on the leader node only.

Fixed a bug where bihactl init --convert failed when executed in a Postgres Pro Enterprise instance with configured pg_proaudit.

Fixed an issue of multiple error messages caused by large heartbeats that might not fit into the shared memory buffer. The issue was solved by decreasing the size of heartbeats written to WAL.

Fixed memory leaks caused by incorrect error handling.

Fixed redundant memory allocation checks.

Fixed an issue where multimaster returned an error when executing read-write transactions containing queries to postgres_fdw foreign tables. The root cause was that postgres_fdw does not support two-phase commit transactions used by multimaster. To fix the issue, the postgres_fdw.read_only_transactions configuration parameter was implemented. When set to on, it enables read-only queries to foreign tables in read-write transactions, which allows seamless operation of multimaster and postgres_fdw.

Fixed an issue of potential transaction commit latency caused by an error in the exchange logic for messages containing information about transaction application on nodes.

Added support for logging of the following event types: ANALYZE, DISCARD ALL, DISCARD PLANS, DISCARD SEQUENCES, DISCARD TEMP (for temporary tables), CHECKPOINT, FETCH, and MOVE.

Added the new event class MISC. This class allows logging of all events (including those mentioned above) not related to other event classes.

Added a new method for logging security events. Events in CEF format can now be logged not only in a separate file but also in syslog.

Added a new event log field: application name. AUTHENTICATE events now contain the name of the initiating application alongside the connection parameters.

Fixed an issue with pg_proaudit failing to log security events in a CEF file.

Fixed an issue with pg_proaudit failing to log events for the INSERT command following CREATE within anonymous code blocks (the DO command) and stored procedures/functions.

Fixed an issue with pg_proaudit overloading a CPU core due to failed log rotation.

Added support for Postgres Pro Enterprise 18.

Added support for Transparent Data Encryption (TDE). The version output of pg_probackup now displays a TDE support indicator.

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.

Added validation to ensure consistency between the port number in PGDATA and the --pgport option. Also added the --force flag to perform backups even when these values mismatch.

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.

Improved the stability of the auto_approve_plans mode for real-time query replanning with the enabled pgpro_multiplan.auto_capturing parameter.

Added the new pgpro_multiplan_remove_template function that removes the specified template plan from the permanent pgpro_multiplan storage.

Added the new pgpro_multiplan_template_hintset_update function that replaces the generated hint set for the template plan with the specified set of custom hints.

Improved messages for errors that can occur when registering queries and freezing query plans.

Changed the logic of specifying values of the pgpro_multiplan.wildcards parameter. Now this parameter accepts a single regular expression rather than a comma-separated list of multiple expressions.

Fixed an issue where the template plan was not identified and applied if constants in the corresponding query were changed.

Fixed an issue in pgpro_multiplan that could cause a server crash when the same query was executed repeatedly due to incorrect handling of the sample_string value.

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.

Implemented automatic cache invalidation at the cluster level using WAL files. It can be enabled using the pgpro_result_cache.consistent and pgpro_result_cache.wal parameters.

Added a possibility to set the pgpro_result_cache.max_memory_size parameter at runtime using the ALTER SYSTEM command.

Added support for the new no_result_cache hint that allows excluding specific queries from caching.

Added two optional limit and offset arguments to the result_cache hint. These arguments allow you to restrict the number of rows returned from cached result sets and skip certain rows before returning.

Fixed an issue that could occur in pgpro_result_cache when caching a large number of simple queries by changing the algorithm for storing cached results.

Fixed a segmentation fault that could occur when reloading the configuration file after the pgpro_result_cache.consistent parameter was set to on.

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:

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.