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

fixing some documentation errors

Browse Source
This commit is contained in:
Christian Kruse
2014-03-10 15:48:44 +01:00
parent 653e11c2a7
commit 2d48d5aee4
1 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
README.rst
View File

@@ -625,18 +625,18 @@ Now restore to the original configuration by stopping
primary server, then bringing up "node2" as a standby with a valid
``recovery.conf`` file.
Stop the "node2" server::
Stop the "node2" server and type the following on "node1" server::
repmgr -f /var/lib/pgsql/repmgr/repmgr.conf standby promote
Now the original primary, "node1" is acting again as primary.
Now the original primary, "node1", is acting again as primary.
Start the "node2" server and type this on "node1"::
Start the "node2" server and type this on "node2"::
repmgr standby clone --force -h node2 -p 5432 -U postgres -R postgres --verbose
Verify the roles have reversed by attempting to insert a record on "node"
and on "node1".
Verify the roles have reversed by attempting to insert a record on "node1"
and on "node2".
The servers are now again acting as primary on "node1" and standby on "node2".