fa66e72c2f
As the witness server does not, by definition, ever have an entry in pg_stat_replication, we need to check its "attached" status by connecting to the witness server itself and querying the reported upstream node ID (which should be set by the witness server repmgrd). If this matches the current primary node ID, we count it as attached.
repmgr: Replication Manager for PostgreSQL
repmgr is a suite of open-source tools to manage replication and failover
within a cluster of PostgreSQL servers. It enhances PostgreSQL's built-in
replication capabilities with utilities to set up standby servers, monitor
replication, and perform administrative tasks such as failover or switchover
operations.
repmgr 4 is a complete rewrite of the existing repmgr codebase, allowing
the use of all of the latest features in PostgreSQL replication.
PostgreSQL 11, 10, 9.6 and 9.5 are fully supported. PostgreSQL 9.4 and 9.3 are supported, with some restrictions.
repmgr is distributed under the GNU GPL 3 and maintained by 2ndQuadrant.
BDR support
repmgr 4 supports monitoring of a two-node BDR 2.0 cluster on PostgreSQL 9.6
only. Note that BDR 2.0 is not publicly available; please contact 2ndQuadrant
for details.
Documentation
The main repmgr documentation is available here:
The README file for repmgr 3.x is available here:
https://github.com/2ndQuadrant/repmgr/blob/REL3_3_STABLE/README.md
Files
CONTRIBUTING.md: details on how to contribute torepmgrCOPYRIGHT: Copyright informationHISTORY: Summary of changes in eachrepmgrreleaseLICENSE: GNU GPL3 details
Directories
contrib/: additional utilitiesdoc/: DocBook-based documentation filesexpected/: expected regression test outputscripts/: example scriptssql/: regression test input
Support and Assistance
2ndQuadrant provides 24x7 production support for repmgr, including
configuration assistance, installation verification and training for
running a robust replication cluster. For further details see:
There is a mailing list/forum to discuss contributions or issues:
The IRC channel #repmgr is registered with freenode.
Please report bugs and other issues to:
Further information is available at https://repmgr.org/
We'd love to hear from you about how you use repmgr. Case studies and news are always welcome. Send us an email at info@2ndQuadrant.com, or send a postcard to
repmgr
c/o 2ndQuadrant
7200 The Quorum
Oxford Business Park North
Oxford
OX4 2JZ
United Kingdom
Thanks from the repmgr core team.
- Ian Barwick
- Jaime Casanova
- Abhijit Menon-Sen
- Simon Riggs
- Cedric Villemain
Further reading
- repmgr documentation
- https://blog.2ndquadrant.com/repmgr-3-2-is-here-barman-support-brand-new-high-availability-features/
- https://blog.2ndquadrant.com/improvements-in-repmgr-3-1-4/
- https://blog.2ndquadrant.com/managing-useful-clusters-repmgr/
- https://blog.2ndquadrant.com/easier_postgresql_90_clusters/