github/repmgr
1
0
Fork 0
mirror of https://github.com/EnterpriseDB/repmgr.git synced 2026-03-25 16:16:29 +00:00
Code Issues Packages Projects Releases 1 Wiki Activity

Specify that we can use -f option to indicate where the repmgr.conf

Browse Source 
is
This commit is contained in:
Jaime Casanova
2010-10-21 01:15:21 -05:00
parent ff511f19b4
commit c3595ad89e
1 changed files with 8 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
README
View File

@@ -62,7 +62,8 @@ pg_ctl -D /your_data_directory_path start
* standby promote * standby promote
Allows manual promotion of a specific standby into a new primary in the event of a failover Allows manual promotion of a specific standby into a new primary in the event of a failover
This needs to be executed on the same directory where the repmgr.conf is in the standby. This needs to be executed on the same directory where the repmgr.conf is in the standby or
then use the -f option to indicate where the repmgr.conf is.
Doesn't need any additional arguments: Doesn't need any additional arguments:
./repmgr standby promote ./repmgr standby promote
@@ -70,12 +71,13 @@ Doesn't need any additional arguments:
That will restart your standby postgresql service That will restart your standby postgresql service
* standby follow [node to be followed] * standby follow
Allows the standby to re-point itself to a new primary indicated as a parameter. Allows the standby to re-point itself to a new primary indicated as a parameter.
This needs to be executed on the same directory where the repmgr.conf is in the standby. This needs to be executed on the same directory where the repmgr.conf is in the standby or
then use the -f option to indicate where the repmgr.conf is.
./repmgr standby follow 10.68.1.162 ./repmgr standby follow
PRE-REQUISITES PRE-REQUISITES
@@ -108,10 +110,10 @@ To make node2 and node3 be standbys of node1, execute this on both nodes (node2
repmgr -D /var/lib/postgresql/9.0 standby clone node1 repmgr -D /var/lib/postgresql/9.0 standby clone node1
If we lose node1 we can run on node2: If we lose node1 we can run on node2:
repmgr standby promote repmgr -f /home/postgres/repmgr.conf standby promote
which makes node2 the new master, we then run on node3: which makes node2 the new master, we then run on node3:
repmgr standby follow node2 repmgr standby follow
to make node3 follow node2 (rather than node1) to make node3 follow node2 (rather than node1)