Added support for indexes and TOAST-tables when estimating their compression ratio using the cfs_estimate function.

Improved error messages that are logged for damaged CFS blocks. Now the error message includes an exit code and an error message from the corresponding compression library.

Fixed an issue where enabled CFS could slow the DROP DATABASE execution. The issue occurred because system interrupts were not processed properly while the command was waiting to acquire a lock for cfs_gc_lock_file.

Added the new aqo_storage_usage function that allows you to get current and maximum sizes of aqo storage and allocated dynamic shared memory.

Optimized the internal structure of the aqo_data storage, as well as improved the mechanisms for allocating dynamic shared memory and lock usage when working with storage data. These enhancements allowed fixing an issue with updating aqo_data storage that was caused by exclusive locks on the underlying hash table and resulted in constant growing of idle in transaction sessions and unstable aqo operation.

Fixed a segmentation fault that could occur after aborting a nested autonomous transaction for which aqo was used. Now aqo checks the nesting level of autonomous transactions and does not clear its local cache when aborting nested transactions.

Added the pg_proaudit.log_file_mode configuration parameter that specifies permissions for new event log files created by pg_proaudit. Note that regardless of this parameter, the server owner always retains access to the log files.

Added a new event field for all types of events logged in CSV files and syslog: IP address of the event source. Previously, this field was displayed only for AUTHENTICATE events logged in the CEF format.

Extended the use of the pg_proaudit.log_rows configuration parameter that enables or disables logging of the number of rows affected by an SQL command. Now the number of affected rows is written for all formats of logged events.

Added validation of the unique ID of the event (UUID) to avoid invalid memory access.

Fixed an issue with incorrect filling of the dst field for events logged in CEF format.

Fixed an issue with excessive memory usage when processing DISCONNECT events. Previously, a hash table sized proportionally to max_connections caused unnecessary memory consumption when the value was large. The data is now stored more efficiently.

Fixed a parser error in pg_proaudit. Previously, pg_proaudit left some characters unescaped when logging events in the CEF format. Now, symbols are escaped correctly in accordance with the CEF specification.

Added support for absolute paths in the --wal-file-path option.

Fixed incremental backups in PAGE mode with the --stream option. With this combination of parameters, WAL files are now correctly saved both inside the backup and in a separate archive.

Added support for the --exclude-path option to exclude specific files or directories from backup in PRO mode.

Optimized the backup performance by excluding temporary files of the postmaster process.

Fixed an incorrect package name in the error message that appeared when the pgpro_bindump failed to load libpb3_encoder.so. The message now correctly recommends installing the libpb3-encoder package instead of the erroneous libpgprobackup3.

Fixed an issue with the CFS garbage collector (GC) being blocked by the backup process, potentially causing write locks during long backups. Both processes now lock only specific data files briefly, avoiding mutual blocking.

Implemented the ability to restore baselines and template plans from plan backups. For this, the pgpro_multiplan_restore function now accepts the baseline and template values for the plan_type argument and contains the new wildcards argument for template plans. Also added the following arguments to this function: sample_string to specify the query with constants and status for future usage.

Implemented the ability to add plans to a baseline using the pgpro_multiplan_register_query and pgpro_multiplan_freeze functions. The last function now can accept the baseline value for the plan_type argument.

Implemented the ability for pgpro_multiplan to register executed prepared statements automatically when the pgpro_multiplan.auto_tracking parameter to is set to on.

Added the new pgpro_multiplan_enable, pgpro_multiplan_enable_baseline, and pgpro_multiplan_enable_template functions that allow enabling and disabling certain existing plans.

Renamed the following functions:

Removed the constants and prep_consts fields from the pgpro_multiplan_captured_queries view. These fields were redundant since query constants are contained in the sample_string field value.

Fixed an issue that could cause an assertion failure when trying to freeze the same plan for the second time.

Fixed an issue that could cause an assertion failure when trying to register a query with the DO NOTHING rule.

Fixed an issue that could cause an assertion failure when using the pgpro_multiplan_register_query function with incorrect optional arguments specifying types of query parameters.

Fixed a segmentation fault that could occur when trying to register a query with a common table expression (CTE) or INSERT ... SELECT.

Fixed an issue where the sample_string values for baselines were saved with parameters rather than constants, which could cause errors when managing these baselines, in particular, when updating their costs using the pgpro_multiplan_update_baseline_cost function.

Fixed an issue where baselines did not save non-default values of configuration parameters, which could cause queries to produce plans different from fixed plans in another environment.

Fixed an issue with incorrect check of the table_hash value for template plans, which could cause applying these plans to inappropriate queries.

Fixed an issue with memory allocation that could occur in pgpro_result_cache with the enabled pgpro_result_cache.consistent parameter when executing a very large number of queries in one transaction.

Fixed an issue that could occur when using the result_cache hint with the offset and limit arguments if the size of the returned result set exceeded the pgpro_result_cache.max_entry_size limit.

Improved logging mechanism. Log messages are more consistent and informative. When a cron job executor background worker is started, the database manager now writes a log message containing the worker's process identifier (PID). This makes it easier to trace worker activity and correlate log entries.

Fixed an issue with the schedule.get_self_id() function returning an incorrect job ID for cron jobs. Now schedule.get_self_id() works as expected in both scheduled and one-time jobs, returning the proper job ID.

Fixed an issue with deactivating a cron job with next_time_statement. Previously, if this job was deactivated while being executed, it could still remain active. Now, the job is immediately deactivated regardless of its execution state.

Fixed excessive memory consumption by a query that used pgpro_stats with pgpro_stats.track set to all. With this setting, a function that assigned plan IDs was called multiple times, and the accumulated memory was not optimally released.

Updated autopreparing and pgpro_stats to fix issues that could occur with autoprepared query normalization in pgpro_stats. Now for proper query normalization, autopreparing stores the cached plan together with certain additional information to be passed to pgpro_stats when the query is executed.

Improved the utility output to include the used preset and display the correct format of date and time when configuration parameters were applied.

Updated presets to improve performance of Postgres Pro.

Fixed an issue where the shared_buffers configuration parameter was calculated incorrectly when using initdb with the enabled pgpro_tune extension. This issue could cause the command to run slower.