A.6. 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.6.1. Core and Extensions #

  • Added a possibility to push down the joins like JOIN UNIQUE INNER to 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_graph view 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, and rgid containing CSN and XID of the oldest transaction in the cluster, along with transaction's replication group number.

  • Added the csn_max_snapshot_shift configuration parameter that enables checking the imported snapshots in pg_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.6.2. Management Utilities #

  • Updated the text of the messages sent when trying to get the topology configuration sent by the shardmanctl cluster topology command on an uninitialized cluster, as well as lowered the logging level for this case.

  • Fixed the shardmanctl bench run command to avoid long delays before its execution.

  • Added the shardmanctl config update credentials command 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, and shardmanctl config get commands, 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 rollback command 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 has max_connections, max_prepared_transactions, or max_worker_processes parameters.

    • The shardmanctl config revisions command outputs revision_id that is the timestamp of the command that resulted in the Shardman configuration change, host that is the host from which the appropriate command was executed, user that is the user who executed the command, and command that is the command itself.

    • The shardmanctl config revisions set command 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 get command outputs the current full cluster specification or the configuration of the specified revision. The --choose-revision option enables an interactive mode of choosing the configuration of the specified revision.

    • The shardmanctl config revisions rm command deletes a specified configuration revision from the history.

  • Modified the role description in sdmspec.json.

pdf