Updated the mechanism of creating managed objects.

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

Improved CFS performance that now uses compression contexts with the default compression library of zstd.

Changed the behavior of the cfs_compression_ratio function. Now the function returns 1 for uncompressed relations.

Added the cfs_is_relation_compressed function to check whether the specified relation is compressed.

Optimized the mechanism of aqo learning. Now aqo ignores plan nodes that do not affect cardinality estimation, for instance Materialized and Sort nodes. These ignored nodes no longer write aqo details in the EXPLAIN output and are not added to aqo statistics.

Changed the implementation of the least recently used (LRU) cache mechanism for the auto mode. Now aqo uses two distinct caches for aqo_data and aqo_query_texts. When the aqo.dsm_size_max limit is reached, the LRU algorithm first removes data from aqo_query_texts, if any, and only then from aqo_data.

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

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

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.

Added the transition from and to the standby mode for the cluster and keeper with the shardmanctl cluster standby enable and shardmanctl cluster standby disable commands.

Added automatic creation of replication slots on primary and standby nodes.

Improved the logic of syncpoint file generation based on WAL processing.

Added the feature to view storage files with shardmanctl files list and shardmanctl files get commands.

Added the stopping of pg_receivewal before a standby cluster is initialized from a backup with shardmanctl probackup restore.

Added automatic update of configuration options of a standby cluster to follow the configuration changes of the primary cluster on the Main data center to further apply them on the Backup data center.

Added the shardmanctl cluster standby config command that creates a configuration file for a Backup data center.

Added the ability to manage standby clusters in terms of the primary shards and standby nodes by using options --lost-shards, --lost-nodes, and -s/--soft to shardmanctl cluster standby disable command.

Allowed avoiding situations when CSN is not written to the WAL due to no writing load with the ShardSpec.noopTransactionMonitorTimeout parameter.

Updated the shardmanctl cluster status command that now can show status of a cluster in standby mode.

Added a feature to synchronize the cluster instance on the Backup data center with the cluster instance in the Main data center with the shardmanctl cluster standby catchup command.

Added a shardmand mechanism that allows showing the services that are currently running in the system.

Added a feature to convert a JSON store dump into binary format of the distributed configuration storage with the shardmanctl store convert command.

Added the shardmanctl cluster maintenance set command to manage the maintenance mode on the specified PostgreSQL instances in a cluster.

Updated logic for working with foreign tools that are initiated with shardmand and shardmanctl by adding new environment variables SDM_PG_MAJOR,SDM_BIN_PATH, and SDM_PROBACKUP_PATH, and -bin-path, probackup-path, and -pg-major common options.

Added the shardmanctl store conflicts command to show the store conflicts.

Improved the revision storage logic by updating the shardmanctl commands.

Updated the shardmanctl cleanup command to work with the new configuration storage.

Updated shardmanctl store commands to support the distributed storage.

Updated the discover mechanism. Added support for two parallel running shardmand on one node.

Updated the node deleting process that now includes deleting information about these nodes from the configuration storage.

Allowed normalizing the distributed storage configuration based on the current node cluster configuration with shardmanctl store normalize.

Allowed deleting of a host from the distributed storage after deleting of the last DB instance on that host.

Removed the DataDir configuration parameter. Now it is required to use the --data-dir parameter or the SDM_DATA_DIR environment variable instead.

Allowed merging incremental backups with the shardmanctl probackup merge --merge-from-id and shardmanctl probackup merge --merge-interval command options.

Added the buffer management options for the shardmanctl probackup command.

Added the shardmanctl probackup retention command to set the backup retention policy for an instance or directory and launch backup merge or purge according to the specified parameters.

Added the pgpro_bindump loading check in shared_preload_libraries and walsender_plugin_libraries.

Updated shardmanctl probackup validate, shardmanctl probackup set-config, shardmanctl probackup show-config and deleted the shardmanctl probackup checkdb.

Adjusted the backup process to work with the S3-compatible storage.

Added a feature that allows keeping or deleting all unmanaged tables with --copy-local-tables when adding a new shard.

Added the --for-upgrade parameter for the shardmanctl restart command. Also added the --with-restart parameter for the shardmanctl upgrade command.

Added a feature to send PSQL commands to a specific shard with the shardmanctl psql command.

Added a feature to form the connection string for one specified shard with shardmanctl getconnstr --shard command option.

Added a feature to specify the socket with the --ipc-socket shardmand option.

Added occupied port verification for the following commands to prevent their hanging: shardmanctl init, shardmanctl nodes add, shardmanctl shard add.

Added support for the SDM_SERVER_HOST variable that defines whether an instance belongs to shardmand. Also added support for several hosts with the shardmanctl --server-host command.

Added a feature to stop or start specific instances with shardmanctl nodes start, shardmanctl nodes stop, shardmanctl shard start, and shardmanctl shard stop by specifying a PostgreSQL port in --node=host:port.

Prohibited to run shardmanctl and shardmand under the root user.

Updated shardmand that now does not start if the directory does not have the required permissions.

Updated the shardmanctl cluster status command that now does not include the nodes of referee or referee_with_wal instances from the output, if the command is executed for a cluster in the standby mode.

Updated the shardmanctl config get and shardmanctl config generate command output that now hide the fields with no specified values.

Updated the shardmanctl commands to accept the specification file in YAML format and define the format automatically.

Improved transferring logic of the environment variable values for the shardcmanctl bench commands.

Improved logging for the cluster instance management commands.

Updated the cluster and shard stopping process. Now primary node fully stops first, only then followed by standbys when running the commands shardmanctl cluster stop, shardmanctl shard stop, shardmanctl nodes stop.

Updated the shardmanctl status, shardmanctl status transactions, shardmanctl rebalance, shardmanctl restart, and shardmanctl restart rolling commands so that they run on the cluster level, thus changing them to shardmanctl cluster status, shardmanctl cluster status transactions, shardmanctl cluster rebalance, shardmanctl cluster restart, and shardmanctl cluster restart rolling

Updated the shardmanctl set and shardmanctl unset command syntax, now they are shardmanctl params set and shardmanctl params unset.

Updated the shardmanctl params unset that now cannot be called for walsender_plugin_libraries.

Adapted the Postgres Pro Shardman utilities to work with shardman_fdw.

Updated the shardmanctl config get command that now runs without meta lock.

Improved the dictionary check logic for shardmanctl cluster status that considers the core changes.

Improved the consistency check for cluster indexes, extensions, procedure languages, sequence, users, tables, collations, tablespaces, schemas, and functions with different --filter options of the shardmanctl schema verify command.

Allowed executing commands outside of the transaction block with the --no-transaction flag of the shardmanctl forall command.