Tue 15 February, 2022
repmgr 5.3.1 is a minor release.
If repmgrd is in use, it should be restarted on all nodes where it is running.
If upgrading from repmgr 5.2.1 or earlier, a PostgreSQL restart is required.
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.