repmgr 4.3.1 will be a minor release. Note that the changes listed here are listed for inclusion in a potential 4.3.1 release, but it is not yet certain whether this will take place, in which case all changes will be folded into the repmgr 4.4 release.
repmgr: when executing repmgr standby switchover, if --siblings-follow is not supplied, list all nodes which repmgr considers to be siblings (this will include the witness server, if in use), and which will remain attached to the old primary.
repmgr: when executing repmgr standby switchover, ignore nodes which are unreachable and marked as inactive. Previously it would abort if any node was unreachable, as that means it was unable to check if repmgrd is running.
However if the node has been marked as inactive in the repmgr metadata, it's reasonable to assume the node is no longer part of the replication cluster and does not need to be checked.
Ensure BDR2-specific functionality cannot be used on BDR3 and later.
The BDR support present in repmgr is for specific BDR2 use cases.
repmgr: when executing repmgr standby clone in --dry-run mode, ensure provision of the --force option does not result in an existing data directory being modified in any way.
repmgr: when executing repmgr primary register with the --force option, if another primary record exists but the associated node is unreachable (or running as a standby), set that node's record to inactive to enable the current node to be registered as a primary.
repmgr: when executing repmgr standby switchover, don't abort if one or more nodes are not reachable and they are marked as inactive.
repmgrd: fix memory leak which occurs while the monitored PostgreSQL node is not running.