Log message:
repmgr: updated to 5.3.1

repmgr 5.3.1 is a minor release.

A.1.1. Bug fixes

Fix upgrade path from repmgr 4.2 and 4.3 to repmgr 5.3.

repmgrd: ensure potentially open connections are closed.

In some cases, when recovering from degraded state in local node monitoring, new \ 
connection was opened to the local node without closing the old one, which will \ 
result in memory leakage.

Log message:
revbump for icu and libffi

Log message:
databases: Replace RMD160 checksums with BLAKE2s checksums

All checksums have been double-checked against existing RMD160 and
SHA512 hashes

The following distfiles could not be fetched (some may be only fetched
conditionally):

./databases/cstore/distinfo D6.data.ros.gz
./databases/cstore/distinfo cstore0.2.tar.gz
./databases/cstore/distinfo data4.tar.gz

Log message:
repmgr: updated to 5.3.0

repmgr 5.3.0 is a major release.

This release provides support for PostgreSQL 14, released in September 2021.

A.1.1. Improvements

repmgr standby switchover: Improve handling of node rejoin failure on the \ 
demotion candidate.

Previously repmgr did not check whether repmgr node rejoin actually succeeded on \ 
the demotion candidate, and would always wait up to node_rejoin_timeout seconds \ 
for it to attach to the promotion candidate, even if this would never happen.

This makes it easier to identify unexpected events during a switchover \ 
operation, such as the demotion candidate being unexpectedly restarted by an \ 
external process.

Note that the output of the repmgr node rejoin operation on the demotion \ 
candidate will now be logged to a temporary file on that node; the location of \ 
the file will be reported in the error message, if one is emitted.

repmgrd: at startup, if node record is marked as "inactive", attempt \ 
to set it to "active".

This behaviour can be overridden by setting the configuration parameter \ 
repmgrd_exit_on_inactive_node to true.

repmgr node rejoin: emit rejoin target note information as NOTICE.

This makes it clearer what repmgr is trying to do.

repmgr node check: option --repmgrd added to check repmgrd status.

Add %p event notification parameter providing the node ID of the former primary \ 
for the repmgrd_failover_promote event.

A.1.2. Bug fixes

repmgr standby clone: if using --replication-conf-only on a node which was set \ 
up without replication slots, but the repmgr configuration was since changed to \ 
use_replication_slots=1, repmgr will now set slot_name in the node record, if it \ 
was previously empty.

repmgrd: rename internal shared library functions to minimize the risk of \ 
clashes with other shared libraries.

This does not affect user-facing SQL functions. However an upgrade of the \ 
installed extension version is required.

repmgrd: ensure short option -s is accepted.

Log message:
databases: Remove SHA1 distfile hashes

Log message:
revbump for textproc/icu

Log message:
repmgr: updated to 5.2.1

repmgr 5.2.1 is a minor release.

A.1.1. Improvements

repmgr standby clone: option --recovery-min-apply-delay added, overriding any \ 
setting present in repmgr.conf.

A.1.2. Bug fixes

Configuration: fix parsing of replication_type configuration parameter.

repmgr standby clone: handle case where postgresql.auto.conf is absent on the \ 
source node.

repmgr standby clone: in PostgreSQL 11 and later, an existing data directory's \ 
permissions will not be changed to 0700 if they are already set to 0750.

repmgrd: prevent termination when local node not available and \ 
standby_disconnect_on_failover is set.

repmgrd: ensure reconnect_interval is correctly handled.

repmgr witness --help: fix witness unregister description.

Log message:
*: Recursive revbump from textproc/icu-68.1

Log message:
repmgr: updated to 5.2.0

repmgr 5.2.0 is a major release.

This release provides support for PostgreSQL 13, released in September 2020.

This release removes support for PostgreSQL 9.3, which was designated EOL in \ 
November 2018.

A.1.1. General improvements

Configuration: support include, include_dir and include_if_exists directives \ 
(see configuration file include directives).

repmgr standby switchover: Improve sanity check failure log output from the \ 
demotion candidate.

If database connection configuration is not consistent across all nodes, it's \ 
possible remote repmgr invocations (e.g. during switchover, from the promotion \ 
candidate to the demotion candidate) will not be able to connect to the \ 
database. This will now be explicitly reported as a database connection failure, \ 
rather than as a failure of the respective sanity check.

repmgr cluster crosscheck / repmgr cluster matrix: improve text mode output \ 
format, in particular so that node identifiers of arbitrary length are displayed \ 
correctly.

repmgr primary unregister: the --force can be provided to unregister an active \ 
primary node, provided it has no registered standby nodes.

repmgr standby clone: new option --verify-backup to run PostgreSQL's \ 
pg_verifybackup utility after cloning a standby to verify the integrity of the \ 
copied data (PostgreSQL 13 and later).

repmgr standby clone: when cloning from Barman, setting --waldir (PostgreSQL 9.6 \ 
and earlier: --xlogdir) in pg_basebackup_options will cause repmgr to create a \ 
WAL directory outside of the main data directory and symlink it from there, in \ 
the same way as would happen when cloning using pg_basebackup.

repmgr standby follow: In PostgreSQL 13 and later, a standby no longer requires \ 
a restart to follow a new upstream node.

The old behaviour (always restarting the standby to follow a new node) can be \ 
restored by setting the configuration file parameter standby_follow_restart to \ 
true.

repmgr node rejoin: enable a node to attach to a target node even the target \ 
node has a lower timeline (PostgreSQL 9.6 and later).

repmgr node rejoin: in PostgreSQL 13 and later, support pg_rewind's ability to \ 
automatically run crash recovery on a PostgreSQL instance which was not shut \ 
down cleanly.

repmgr node check: option --db-connection added to check if repmgr can connect \ 
to the database on the local node.

repmgr node check: report database connection error if the --optformat was provided.

Improve handling of pg_control read errors.

It is now possible to dump the contents of repmgr metadata tables with pg_dump.

A.1.2. repmgrd enhancements

Following additional parameters can be provided to failover_validation_command:

%n: node ID
%a: node name
%v: number of visible nodes
%u: number of shared upstream nodes
%t: total number of nodes
Configuration option always_promote (default: false) to control whether a node \ 
should be promoted if the repmgr metadata is not up-to-date on that node.

A.1.3. Bug fixes

repmgr standby clone: fix issue with cloning from Barman where the tablespace \ 
mapping file was not flushed to disk before attempting to retrieve files from \ 
Barman.

repmgr node rejoin: ensure that when verifying a standby node has attached to \ 
its upstream, the node has started streaming before confirming the success of \ 
the rejoin operation.

repmgrd: ensure primary connection is reset if same as upstream.

Log message:
Revbump for icu