Ian Barwick be494f0d5f standby clone: minimize requirement to check upstream data directory location
repmgr has always insisted on determining the upstream's data directory
location, which requires superuser permissions (or from PostgreSQL 10,
membership of the default role "pg_read_all_settings").

Knowledge of the data directory location was required to implement rsync
cloning (now deprecated), but with pg_basebackup the minimum permission
requirement is now only a normal user with access to the repmgr metadata
and a user with replication permissions. The ability to determine the
data directory location is only required if the user specifies the
--copy-external-config-files option, which needs to be able to determine
the data directory to work out which configuration files are located
outside it.

This patch makes it possible to clone a standby with minimum
permissions, with appropriate checks for available permissions if
--copy-external-config-files is provided.

Implements part of GitHub #536 and addresses issue raised in #586.
2019-10-23 10:46:40 +09:00
2019-01-14 10:04:20 +09:00
2017-11-20 15:18:21 +09:00
2019-01-21 14:54:35 +09:00
2019-01-21 14:54:35 +09:00
2019-10-16 11:04:37 +09:00
2019-10-16 11:04:37 +09:00
2019-01-21 14:54:35 +09:00
2017-09-11 10:21:20 +09:00
2019-10-17 17:13:18 +09:00
2019-01-21 14:54:35 +09:00
2019-01-23 10:28:48 +09:00
2017-09-08 13:27:39 +09:00
2019-01-21 14:54:35 +09:00
2019-10-16 11:04:37 +09:00
2017-09-11 11:00:48 +09:00
2019-04-03 11:12:48 +09:00
2019-10-16 11:04:37 +09:00
2019-10-16 11:04:37 +09:00
2019-04-30 15:53:24 +09:00
2019-01-21 14:54:35 +09:00
2018-03-30 14:24:36 +09:00
2019-01-21 14:54:35 +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 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:

repmgr 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://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%