Ian Barwick
d6c27f8938
Standardize quoting in log messages
2017-10-04 09:34:59 +09:00
Ian Barwick
dd06ed2b92
"repmgr bdr register": actually exit on various error conditions.
...
Error message was displayed but execution continued.
2017-10-04 09:34:55 +09:00
Ian Barwick
97957287b4
Update "repmgr bdr --help" output
2017-10-04 09:34:50 +09:00
Ian Barwick
b6cd816923
Tidy up some log output
2017-09-12 11:08:41 +09:00
Ian Barwick
a9f4a027a7
pgindent run
2017-09-11 11:14:13 +09:00
Ian Barwick
e4f7dc8234
Add copyright notices
2017-09-08 13:27:39 +09:00
Ian Barwick
0ac16f7630
Add more --help output
2017-08-16 17:49:46 +09:00
Ian Barwick
4efc8fb9ce
Add placeholder functions for "repmgr $command --help"
...
There are now too many options to sensibly fit into general --help
output; we'll add separate output for each repmgr command, e.g.
"repmgr node --help".
2017-08-16 13:24:14 +09:00
Ian Barwick
10ef30096c
"node check": add server role check
2017-08-14 22:57:09 +09:00
Ian Barwick
3b2158edbf
Initialise variables, where appropriate
2017-08-14 15:11:42 +09:00
Ian Barwick
2594a46a4f
Limit repmgr installation on a BDR cluster to two nodes
2017-07-13 14:10:08 +09:00
Ian Barwick
7eadbf6b17
Various improvements to "repmgr bdr register/unregister"
2017-07-12 22:38:03 +09:00
Ian Barwick
0a1addfdc0
When registering a BDR node, sync repmgr.nodes from another node
...
If a BDR node is added via bdr_group_join(), repmgr.nodes will
start off empty, so we'll need to sync it ourselves before adding
it to the repmgr replication set.
2017-07-12 10:11:25 +09:00
Ian Barwick
1cccb1dd5a
Add "repmgr bdr unregister"
2017-07-12 10:11:21 +09:00
Ian Barwick
71a0871232
Add "repmgr bdr register"
2017-07-11 15:38:58 +09:00