Added handling of SIGILL signals to crash_info processing.

Added details, like process start time and query text at planning, to crash_info output files.

Fixed incorrect function names in the first 2-3 lines of crash_info backtrace stacks.

Fixed possible data truncation at the end of SQL query dump files. Previously, a buffer overflow during SQL query dumping could result in incomplete writes, causing truncated data at the end of files produced by crash_info.

Fixed handling of crash information signals (sent using the kill command) by backends. Previously, the first signal would flush crash_info information to the log, but the process would continue running without producing a core dump, even if configured, and only the second signal would terminate the backend and generate the core dump as expected.

Fixed compatibility of CFS with the ALTER TABLESPACE ... SET/RESET commands.

Fixed an issue with memory allocation within a critical section in the implementation of VACUUM ANALYZE for compressed tables.

Fixed a segmentation fault, which could occur when using postgres_fdw with autonomous transactions.

Fixed loss of temporary tables from parent transaction on autonomous transaction rollback.

Fixed an issue with empty xact_start columns in the pg_stat_activity view for backends executing autonomous transactions.

Improved the way nodes delete old synchronization points. Previously, every node deleted only a part of the synchronization point table and replicated changes to other nodes. This could cause synchronization issues and inability to delete old synchronization points. Now, every node deletes all synchronization points and does not replicate changes to other nodes.

Fixed potential node hanging during catchup when attempting to process aborted DDL transactions in a cluster of three or more nodes.

Increased line size for EXPLAIN output as some Oracle catalog queries have long filter conditions. The line size was increased to the value of 3000.

Fixed a crash with column options on non-existing columns. If the Oracle table has fewer columns than the Postgres Pro and one of these extra columns has a column option set, oracle_fdw would write past the end of an array, leading to memory corruption and crashes. Now options for such columns are ignored.

Added new object types: CATALOG RELATION and CATALOG FUNCTION.

Added new event fields: UUID, XID, and VXID. Now it is possible to identify an event by its UUID and transaction IDs (if applicable).

The behavior of the pg_proaudit.log_catalog_access configuration parameter was corrected to reflect the new logic of logging for system catalog objects.

Changed the logic of handling disconnection events. Now these events are associated with the corresponding authentication events, so the disconnection events will be logged even in the case when the rule is removed after authentication, but before disconnect.

Fixed an issue where the DISCONNECT event type was not logged for a user who was a member of the role that was set in the logging rule.

Fixed the bug that caused a log entry to be written to an incorrect log file when log file rotation was configured.

Fixed an issue with pg_proaudit failing to log schema creation events.

Corrected the behavior of the logger process when deleting a role from a parallel session configured by the rule.

Added the maintain command to resolve issues that can occur during a forced backup termination.

Added the --lock-lifetime option that sets the timeout for locks. This option is useful for computational environments with a slow network.

Stabilized retaining the initial permissions for directories when running the init command.

Stabilized the checkdb command on a remote host.

Improved the stability of the point-in-time recovery (PITR) with validation.

Fixed the “SignatureDoesNotMatch” error that could occur when connecting to the VK Cloud S3 storage.

Fixed an incorrect behavior that could occur when launching the wait for a WAL streaming thread in the ARCHIVE WAL delivery mode.

Added support for pgpro_stats 1.9.

Added a possibility to define the mode of collecting relation sizes globally through the pgpro_pwr.relsize_collect_mode extension parameter or for a server through the set_server_size_sampling function parameter.

Enabled fine-tuning the server statistics collection by calling the set_server_setting function. It allows you to define which statistics should be collected.

Added a preview of storage parameters for tables and indexes in the “Schema object statistics” report section.

Enhanced session tracing to provide more information. Specifically, the new time_info filter attribute controls inclusion of additional information in the session-tracing output, and the pgpro_stats.trace_query_text_size configuration parameter can limit the size of the query in the session-tracing output.

Aligned the names of the explain_* filter attributes of the session tracer with the names of session-tracing configuration parameters.

Changed the format of the statistics dump file and the corresponding save/load routines.

Implemented turning off the session tracer functionality when no session-tracing filters are specified.

Prohibited inclusion of both pgpro_stats and pg_stat_statements in the list of shared_preload_libraries. If both are included, the database server will not start.

Fixed an issue where GUC variables could be overridden when using parallel workers.

Fixed an issue with malformed samples caused by a race condition when pg_wait_sampling.sample_cpu is disabled.