Ian Barwick 36b3782009 Store the replication user in repmgr.nodes
When creating recovery.conf outside of "repmgr standby clone",
there was no way of knowing if a replication user had been
explicitly provided with --replication-user, meaning the value
of "primary_conninfo" would be set to the "conninfo" field of the
node's upstream node record.

We'll add an extra column to store the replication user for each
node so it can be referenced at any time.
2017-06-14 23:27:26 +09:00
2017-04-26 22:49:19 +09:00
2017-05-01 23:34:01 +09:00
2017-05-01 23:34:01 +09:00
2017-04-19 10:12:52 +09:00
2017-05-31 23:01:20 +09:00
2017-06-12 21:27:09 +09:00
2017-04-28 22:00:26 +09:00
2017-04-25 08:22:58 +09:00
2017-04-25 08:22:58 +09:00
2017-04-25 22:26:12 +09:00
2017-04-18 11:26:51 +09:00
2017-06-12 08:39:50 +09:00
2017-04-18 11:26:51 +09:00
2017-04-19 10:12:26 +09:00
2017-04-28 22:00:26 +09:00
2017-05-02 14:25:08 +09:00
2017-05-05 10:50:41 +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.

Commands

repmgr cluster event [--all] [--node-id] [--node-name] [--event] [--event-matching]

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%