Introduced the aqo sandbox mode, which allows working in an isolated environment without touching the main aqo knowledge base. This mode can be turned on either on a primary or a standby node by setting aqo.sandbox to on.

Enhanced aqo wide search (aqo.wide_search = on) to utilize data from multiple neighbors simultaneously. Also, revised its interaction with aqo.min_neighbors_for_predicting to allow queries with fewer than the specified number of data samples to participate in wide search. Previously, such queries were excluded from consideration.

Fixed an array index out-of-bounds issue in the aqo smart statement timeout update logic, as well as incorrect statistics insertion into aqo_query_stats when the arrays were full.

Added support for systems where setuptools version greater than 67.7.2 is installed.

Ended the use of dotted user:group specification at the RPM pre-install stage.

Added logging of security events related to operations with profiles: CREATE PROFILE, ALTER PROFILE, and DROP PROFILE.

Changed the distribution of security events related to functions and stored procedures among the groups of security events: the ALL_DDL group now includes no events related to functions and stored procedures, ALL_PROC includes CREATE, ALTER, and DROP, while ALL_DML includes EXECUTE.

Fixed logging of security events on partitioned tables. Now the SELECT/UPDATE/INSERT/DELETE/TRUNCATE events on a partitioned table get logged if logging rules imply logging of appropriate events for this table. Previously, only events on individual partitions were logged.

Fixed compatibility with the connection pooler. Previously, issues could be encountered when logging AUTHENTICATE and DISCONNECT security events.

Enabled the output of the version command in the JSON format using --format=json.

Added the --all option to the amcheck command, which allows performing all the checks in a single command.

Added support for the include parameter in the configuration file. The contents of the file specified in include gets added to the configuration file instead of this parameter.

Added a possibility to specify an individual number of threads for execution of a backup and its subsequent validation by specifying the --backup-threads and --validate-threads option, respectively.

Changed the priority of setting PGDATA and BACKUP_PATH. Now the values from the command-line options take precedence.

Added validation of WAL files for backups to be merged by the merge command.

An error message that was issued when the validate command run with the --wal option found an archive in the DEGRADED status has been replaced with a warning since backups in this status do not affect the restore correctness as a whole.

Fixed an issue that could occur if the command line was too long.

Fixed an issue that could occur during validation or restore when the PITR from a previous timeline was performed.

Updated pgpro_stats_statements and pgpro_stats_totals views to include fields added to pg_stat_statements. Related functions were updated accordingly.

Streamlined access to views and functions. Specifically, access to the pgpro_stats_archiver, pgpro_stats_vacuum_database, pgpro_stats_vacuum_tables, and pgpro_stats_vacuum_indexes views was granted to all users. Previously, these views required explicitly granting access rights. Access to execution of the pgpro_stats_trace_reset function, which could previously be executed by any user, was restricted to superusers.

Implemented an optimization that lowers the locking time in some cases when copying metrics from the local memory to the shared memory.

Eliminated an excessive check of holding the lock when accessing the hash table of session-tracing filters.

Fixed processing of the pgpro_stats.stats_temp_directory configuration parameter. Previously after the server restart for changes to this parameter value to take effect, the fatal error “pfree called with invalid pointer” could occur when processing this parameter.

Fixed an issue that could occur during session tracing and cause errors “could not write file ""pg_stat/pgpro_stats_filters.trace.tmp"": No such file or directory”. Concurrent writing from different sessions to a trace file is fixed now, so processes can write to the trace file in parallel without collisions.