Ian Barwick 0468e47ef3 repmgrd: improve reconnection handling
Previously, if the server being monitored was not available, repmgrd
would always close the existing connection handle and open a new one.

However, in some cases, e.g. a brief network outage, the existing
connection handle is still good and does not need to be reopened.

This could be particularly problematic if monitoring_history is on,
as this risks leaving orphan sessions on the primary which (given
a sufficiently unstable network) could lead to all available backends
being occupied.

Instead, during an outage we now use a new connection to verify
the server is accessible; if the old connection is still available
(e.g. following a short network interruption) we continue using that;
if  not (e.g. the server was restarted), we use the new one.
2018-08-30 15:47:49 +09:00
2017-11-20 15:18:21 +09:00
2017-11-20 15:18:21 +09:00
2017-11-08 12:09:33 +09:00
2018-01-02 10:19:46 +09:00
2018-01-02 10:19:46 +09:00
2018-08-07 15:22:11 +09:00
2018-08-07 15:22:11 +09:00
2018-04-02 20:54:42 +09:00
2018-04-02 20:54:42 +09:00
2018-01-02 10:19:46 +09:00
2017-09-11 10:21:20 +09:00
2018-04-07 11:46:10 +09:00
2018-08-30 15:47:49 +09:00
2017-09-08 13:27:39 +09:00
2018-07-13 12:09:41 +09:00
2018-07-13 12:09:41 +09:00
2017-09-11 11:00:48 +09:00
2018-08-07 15:22:11 +09:00
2018-06-15 14:30:06 +09:00
2018-07-13 12:09:41 +09:00
2018-03-06 11:00:03 +09:00
2018-01-02 10:19:46 +09:00
2018-01-02 10:19:46 +09:00
2018-03-30 14:24:36 +09:00
2018-01-02 10:19:46 +09:00

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 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. repmgr 4 will support future public BDR releases.

Documentation

The main repmgr documentation is available here:

repmgr 4 documentation

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 to repmgr
  • COPYRIGHT: Copyright information
  • HISTORY: Summary of changes in each repmgr release
  • LICENSE: GNU GPL3 details

Directories

  • contrib/: additional utilities
  • doc/: DocBook-based documentation files
  • expected/: expected regression test output
  • scripts/: example scripts
  • sql/: 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://www.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 v5.5.0 Latest
2024-11-22 14:34:48 +00:00
Languages
C 98.1%
Lex 1.3%
Makefile 0.4%
Perl 0.2%