Enhanced the pgpro_stats extension to give a better understanding of what system resources are used for distributed queries. Now the regular pgpro_stats_statements view shows the gathered statistics for individual statements on the current Shardman node (they can be part of some distributed query), while the pgpro_stats_sdm_statements view shows the gathered statistics for the distributed queries originating from the current node, that is, aggregated from all the participating nodes.

Added the pgpro_pwr package compatible with Shardman. This allows Shardman users to build workload reports.

Improved the EXPLAIN output. If a query plan contains ForeignScan nodes, the EXPLAIN output for queries executed on the remote server can now be included.

Added a new configuration parameter enable_partition_pruning_extra that enables extended subplan pruning logic when building and executing generic plans where the set of useful partitions depends on the prepared query parameters. This allows Shardman to do initial pruning of complex subplans, joins and partial aggregates, in particular.

Added metrics to the shardman.pg_stat_csn view that show delays of the global horizon and the transaction that may cause that delay. They may be useful to research autovacuum issues.

Considerably improved backup and restore with the shardmanctl probackup command. Notable changes are as follows:

Updated the getconnstr and cluster topology commands so that they do not issue a lock on other processes. Previously, some commands failed to receive a connection string because of the locks.

Fixed a panic that could occur on a Shardman cluster configured with PlacementPolicy = manual when a user executed the command shardmanctl cluster repfactor set.

Hid uninformative warnings that pg_dump displayed during execution of shardmanctl nodes add and shardmanctl probackup backup commands.

Removed a lock that was required by the shardmanctl status command. Previously shardmanctl status did not provide any useful information in case a process hung as it was waiting for the lock from that process.

Added the forceSuUserLocalPeerAuth configuration parameter. When enabled, it sets a peer authentication via unix socket for the postgres user unless strictUserHBA is set to true. See sdmspec.json for details.

Added a URL for Prometheus automatic service discovery metrics to shardmand.