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

Fix documentation to always use -h sintax to refer to the node we

Browse Source 
want to clone or connect to, instead of relying on the fact that
for some time putting that argument at last worked.
This commit is contained in:
Jaime Casanova
2012-08-30 02:10:10 -05:00
parent 56d2ae4e81
commit 57aa95f674
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
autofailover_quick_setup.rst
View File

@@ -112,7 +112,7 @@ Log in node2.
Clone the node1 (the current Master):: Clone the node1 (the current Master)::
su - postgres su - postgres
repmgr -d repmgr -U repmgr standby clone node1 repmgr -d repmgr -U repmgr -h node1 standby clone
Start the PostgreSQL server:: Start the PostgreSQL server::
@@ -173,7 +173,7 @@ Log in witness.
Initialize the witness server:: Initialize the witness server::
su - postgres su - postgres
repmgr -d repmgr -U repmgr -h 192.168.1.10 -D $WITNESS_PGDATA -f /etc/repmgr/repmgr.conf witness create node1 repmgr -d repmgr -U repmgr -h 192.168.1.10 -D $WITNESS_PGDATA -f /etc/repmgr/repmgr.conf witness create
It needs information to connect to the master to copy the configuration of the cluster, also it needs to know where it should initialize it's own $PGDATA. It needs information to connect to the master to copy the configuration of the cluster, also it needs to know where it should initialize it's own $PGDATA.
As part of the procees it also ask for the superuser password so it can connect when needed. As part of the procees it also ask for the superuser password so it can connect when needed.