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

Update repmgrd usage examples and help output

Browse Source
This commit is contained in:
Ian Barwick
2014-12-25 10:52:50 +09:00
parent 6f80cd5441
commit 4c64d52afb
2 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
README.rst
View File

@@ -545,7 +545,7 @@ You could now register the standby by typing on "node2"::
However, you can instead start repmgrd::
repmgrd -f /var/lib/pgsql/repmgr/repmgr.conf --verbose > /var/lib/pgsql/repmgr/repmgr.log 2>&1
repmgrd -f /var/lib/pgsql/repmgr/repmgr.conf --daemonize --verbose > /var/lib/pgsql/repmgr/repmgr.log 2>&1
Which will automatically register your standby system. And eventually
you need repmgrd running anyway, to save lag monitoring information.
@@ -1015,6 +1015,8 @@ The output from this program looks like this::
--verbose output verbose activity information
--monitoring-history track advance or lag of the replication in every standby in repl_monitor
-f, --config-file=PATH path to the configuration file
-d, --daemonize detach process from foregroun
-p, --pid-file=PATH write a PID file
repmgrd monitors a cluster of servers.

2
autofailover_quick_setup.rst
View File

@@ -202,7 +202,7 @@ Start the repmgrd daemons
Log in node2 and witness.
su - postgres
repmgrd -f /etc/repmgr/repmgr.conf > /var/log/postgresql/repmgr.log 2>&1
repmgrd -f /etc/repmgr/repmgr.conf --daemonize -> /var/log/postgresql/repmgr.log 2>&1
**Note:** The Master does not need a repmgrd daemon.