Added the crash_info_timer, crash_info_timer_interval, and crash_info_query_threshold configuration parameters that allow profiling long queries in crash_info output files.

Extended the diagnostic information that the crash_info_dump configuration parameter can specify to write in case of a backend crash. By default, now the general information on the signal is dumped and for Linux x64, also the information on the processor state and bytes near RIP (return instruction pointer). All this ensures better diagnostics, in particular, in case of SIGILL (illegal instruction) signals. The way of dumping stack files in case of crashes has also been changed for Linux x64. Besides, memory_context has been removed from the default list of sources to be dumped in order to avoid failures that could occur when writing the diagnostic information.

Improved compressed tablespace operations on s390/s390x architectures.

Improved the compression ratio estimation for tables using the cfs_estimate(relation) function. Note that cfs_estimate(relation) should be used only after a checkpoint to avoid incorrect estimations.

Disabled truncation for compressed relations during vacuum operations.

Removed encryption support for CFS, including the cfs_encryption configuration parameter.

Fixed the race condition when calling the aqo_cleanup function from different sessions.

Fixed an issue where aqo learning data was not saved for queries that use materialization.

Improved the ability of the node to return to normal operation after catchup by accelerating the transaction filter building process at the start of walreceiver.

Fixed a bug that caused recovery hanging and potential data desynchronization when adding a new node.

Fixed unexpected errors in execution of DDL commands that were caused by incorrect processing of catalog cache invalidation messages.

Added support for CEF format for event log files.

Adjusted pg_proaudit output. xid and vxid fields are no longer displayed if they are zero.

Added the --wal-tree option for the add-instance command to store archived WAL files in a tree-like structure. This improves WAL operation performance with large volumes of logs.

Added the postgres-edition field to the show command output in the JSON format to display DBMS edition information.

Improved the --dry-run option operation during tablespace recovery. The operation estimation and plan output are now more precise.

Fixed an issue related to the retention window calculation. The time value is now taken from the host where pg_probackup is running. The retention window is now calculated correctly even with the timezone differences between the servers.

Fixed a problem with the archive-get command operation. The pbk_prefetch directory is now created with correct access rights, inheriting permissions from PGDATA.

Fixed false failure of the checkdb command in the remote mode during concurrent TRUNCATE operations or table drops on standby nodes.

Fixed potential pg_probackup3 failure caused by temporary tables during backup validation using the pgpro_bindump module in the PRO mode.

Fixed a memory leak in pg_probackup3 using the pgpro_bindump module for PTRACK operations.

Fixed an issue that could cause infinite looping in pg_probackup3 when using the pgpro_bindump module.

Fixed an issue with multi-timeline backup in the PTRACK mode in pg_probackup3 using the pgpro_bindump module in the PRO mode.

Added the repack command for changing the compression algorithm and/or compression level of CFS files.

Added the ground command for replacing corrupted blocks with zeros to prevent potential operation failures.

Added the stat command to monitor tablespace statistics.

Added the new pgpro_multiplan.mode parameter that allows you to enable or disable the extension, the use of available plan types, as well as statistics collection.

Added the baseline value for the plan_type field of the pgpro_multiplan_storage view to identify allowed plans.

Renamed the following entities:

Changed the default behavior of statistics collection. Now statistics are not gathered unless you enable this feature using the pgpro_multiplan.mode parameter.

Removed the pgpro_multiplan.enable parameter that is no longer required. Instead, use the pgpro_multiplan.mode parameter.

Added the sample_string field to the pgpro_multiplan_storage view to store a non-parameterized query for which a plan was frozen or added to a set of allowed plans.

Added the planid field to the pgpro_multiplan_captured_queries and pgpro_multiplan_stats views. This field specifies the plan ID compatible with the pgpro_stats extension and allows you to get extended statistics by joining information from the pgpro_multiplan_stats and pgpro_stats_statements views.

Added the pgpro_multiplan_remove_baseline function that removes the specified plan from a set of allowed plans.

Fixed an issue with pgpro_multiplan failing to register queries involving the INTERVAL 'const' notation.

Fixed an issue where plan_hash was not calculated when adding plans for queries with custom hints to a set of allowed plans (baseline). Now such plans can be added to a baseline with correct plan_hash values.

Added the schedule.clean_at_jobs_done and schedule.clean_at_jobs_done functions that can clean schedule.at_jobs_done by removing old records.

Provided the ability to change the next start time for a cron job that has next_time_statement by updating cron, date, dates, or rule using the set_job_attributes() function.

Fixed a segmentation fault caused by invalid memory access when a buffer pointer was used after the underlying buffer was modified by another thread.

Fixed an index scan infinite loop when using multiple ORDER BY clauses.