Changed the name format of crash_info output files to specify date and time with microseconds.

Fixed a bug that could occur when trying to write a query text to crash_info output files.

Fixed backup failures due to erroneous inclusion of unlogged tables and temporary tablespaces. Previously, if such files were deleted during the backup process, pg_probackup3 would treat them as missing and abort the operation.

Fixed incorrect Postgres Pro edition detection in the PRO data source mode for Shardman.

Added the pg_proaudit.log_rows configuration parameter that enables or disables logging of the number of rows affected by an SQL command.

Added a new event log field: connection duration. DISCONNECT events now contain the total connection duration alongside other connection parameters.

Added verification and validation of recovery-target-name in the WAL archive during recovery. This prevents situations where the Postgres Pro cluster fails to start due to an unreachable recovery target. If a named recovery target was created before the last backup, the recovery process now correctly checks its existence.

Added the ability to pass parameters to a remote agent in a configuration file format to improve flexibility when working with backup agents in distributed environments.

Implemented compatibility with the pgpro_cpumeter extension. The pgpro_cpumeter.stat file is now added to the exclusion list during backup.

Fixed an issue where the --skip-block-validation flag was being ignored during backup. Previously, this resulted in an error if the cluster contained pages with invalid checksums in their headers. This is critically important when enabling checksums in older clusters that may have pre-existing checksum issues. Also, a warning is now displayed when --skip-block-validation is used.

Improved backup status reporting. The backup status is now set to DONE before the validation phase. Backup metadata is written twice: before validation and after backup completion. The show command now displays a more accurate backup status during long-running validation checks.

Fixed an issue that could result in a crash if the backup_content.control file was deleted before the DELTA backup.

Restored the possibility to track aggregate statistics for sessions, which had previously been removed as unused. Whether aggregate statistics for the sessions are tracked is controlled by the pgpro_stats.track_sessions configuration parameter.

Improved the behavior of session-tracing functions. The pgpro_stats_trace_insert and pgpro_stats_trace_update functions now fail with an error if some filter attribute is listed in the passed sequence of key-value pairs more than once. If a wrong argument is passed to the pgpro_stats_trace_update function, the filter no longer gets updated. The pgpro_stats_trace_show function now returns exactly the values of explain* attributes that were specified for the filter.

Fixed an issue to avoid crash when two or more constants are marked as having the same location in the SQL statement text.

Added the autovacuum_vacuum_scale_factor and autovacuum_vacuum_insert_scale_factor parameters to the pgpro_tune default.tune preset configuration.

Fixed an issue with pgpro_tune not being able to process preset names with whitespaces when specifying a preset in the initdb PGPRO_TUNE environment variable. Now if pgpro_tune fails, initdb also fails.

Fixed the default.tune preset, which now correctly displays the order of effective_io_concurrency and random_page_cost parameter values depending on the drive type.

Added functions that allow inspecting all types of RUM index pages at a low level.

Fixed a bug that caused scanning of multi-column RUM indexes to return incorrect results. This happened when the index was created with order_by_attach set to true for one of the columns, and a query specified conditions for several index columns, including the one with order_by_attach.