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. In previous releases, using aqo_query_stat_update with arrays of size 20 or more could lead to subsequent statistics updates being written to uncontrolled memory segments. Make sure to install the Postgres Pro on both primary and standby servers to avoid similar memory corruption problems.

Upgraded biha to version 1.4.

Implemented the callbacks to call custom SQL functions, which can notify users or external services about events in the BiHA cluster.

Implemented a mechanism that enables relaxed synchronous replication for the BiHA cluster. To relax synchronous replication restrictions, specify the --sync-standbys-min parameter when initializing the cluster with the bihactl init command, or later by means of the biha.set_sync_standbys_min function.

Added the biha.node_priority configuration parameter that allows you to manage voting by means of setting node priorities in the BiHA cluster.

Added the biha.set_nquorum and biha.set_minnodes functions to configure the biha.nquorum and biha.minnodes configuration parameters independently. Previously, these parameters could only be set together by the biha.set_nquorum_and_minnodes function.

Added the biha.can_vote and biha.can_be_leader configuration parameters that allow you to manage the ability of the BiHA cluster nodes to vote and stand as candidates in elections of the new leader correspondingly.

Added the biha.flw_ro configuration parameter that allows you to determine whether a node can be available for read operations.

Implemented a mechanism that automatically disables reading from the node in the NODE_ERROR state.

Updated the biha.nodes_v view. The view table now also displays the node that the view is queried on.

Changed the way the GUC parameters essential for biha operation are managed. Previously, manual modification of the following parameters was not forbidden: primary_conninfo, primary_slot_name, synchronous_standby_names. However, manual change of the above mentioned parameters could have negative impact on the BiHA cluster operation. Now, when biha is loaded and configured, these parameters are managed by biha only, and you cannot modify them with ALTER SYSTEM.

Optimized the behavior of the BiHA cluster when replication cannot proceed due to deletion of the required WAL files determined in the max_slot_wal_keep_size parameter. In this situation, the node that falls behind transfers to the NODE_ERROR state.

Fixed a bug that caused the reboot of a leader candidate in case it does not know the ID of the old leader.

Fixed an issue with the data directory size growth on the referee node in referee_with_wal mode.

Fixed a bug that caused authentication issues when setting up a BiHA cluster from the existing cluster. The biha extension now uses the same password encryption algorithm that is set in the postgresql.conf file of the converted primary node.

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 compatibility with the connection pooler. Previously, issues could be encountered when logging AUTHENTICATE and DISCONNECT security events.

Fixed logging of security events on partitioned tables by pg_proaudit. 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.

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.

Added support for the --s3-config-file option of restore_command. postgresql.auto.conf must include the restore_command with the --s3-config-file option if the backup was created with this option.

The default value of PG_PROBACKUP_S3_IGNORE_CERT_VER is set to on according to the documentation.

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.

Fixed an issue that could occur when the S3 connection port was specified both in PG_PROBACKUP_S3_PORT and PG_PROBACKUP_S3_HOST. Now the value specified in PG_PROBACKUP_S3_HOST, together with the address, has higher priority.

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.

Fixed an issue with automatic restart of one-time jobs after job interruption.

Fixed schedule.get_active_jobs to properly return the list of currently executed cron jobs.

Fixed an issue where errors occurring during job execution were not properly logged due to a primary key constraint preventing multiple log entries.

Fixed an issue where at job executor would fail when the database manager prematurely released the shared memory segment before the worker had connected to it.

Fixed an issue where schedule.timetable did not display the next execution time of cron jobs with either next_time_statement or an array of dates. Fixed an issue with calculating next execution time for cron jobs that caused job instances to be skipped.

Fixed an issue causing database crashes due to segmentation faults in the job executor background worker.