A.14. Postgres Pro Shardman 14.13.1 #
Release date: 2024-09-12
This release provides new features, optimizations and bug fixes. Major changes are as follows:
A.14.1. Core and Extensions #
Added a possibility to push down the joins like
JOIN UNIQUE INNERto a remote server.Added the shardman.pg_stat_monitor view showing metrics of the Shardman monitor; shardman.pg_stat_net_usage view showing the cumulative network traffic between Shardman cluster nodes; and
shardman.gv_lock_graphview that displays a graph of locks between processes on Shardman cluster nodes including external locks.Added the shardman.oldest_csn view that shows tuple
csn,xid, andrgidcontaining CSN and XID of the oldest transaction in the cluster, along with transaction's replication group number.Added the
csn_max_snapshot_shiftconfiguration parameter that enables checking the imported snapshots inpg_csn_snapshot_import().Introduced new limitations on the types of tables that can be included in logical replication.
Upgraded supported version of pg_probackup to 2.8.3.
A.14.2. Management Utilities #
Updated the text of the messages sent when trying to get the topology configuration sent by the
shardmanctl cluster topologycommand on an uninitialized cluster, as well as lowered the logging level for this case.Fixed the
shardmanctl bench runcommand to avoid long delays before its execution.Added the
shardmanctl config update credentialscommand that updates password or certificate/key of a user to connect to a Shardman cluster.Added the
shardmanctl config revisions,shardmanctl config rollback,shardmanctl config revisions rm, andshardmanctl config getcommands, and added to the console output the information about the host from which the appropriate command was executed and the user who executed it.The
shardmanctl config rollbackcommand makes a rollback of Shardman to one of the previous states of Shardman cluster configuration. This command has the replicas reinitialized when rolling back to the config revision that hasmax_connections,max_prepared_transactions, ormax_worker_processesparameters.The
shardmanctl config revisionscommand outputsrevision_idthat is the timestamp of the command that resulted in the Shardman configuration change,hostthat is the host from which the appropriate command was executed,userthat is the user who executed the command, andcommandthat is the command itself.The
shardmanctl config revisions setcommand allows setting the length of the configuration revision history. Added a hard lower limit on the revision history length of a Shardman cluster configuration. This value cannot be lower than 5. For clusters where the configuration revision history was not tracked, the length is automatically set to the default value of 20.The
shardmanctl config getcommand outputs the current full cluster specification or the configuration of the specified revision. The--choose-revisionoption enables an interactive mode of choosing the configuration of the specified revision.The
shardmanctl config revisions rmcommand deletes a specified configuration revision from the history.
Modified the role description in
sdmspec.json.