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

README: fix typos

Browse Source
This commit is contained in:
Ian Barwick
2017-02-14 10:58:09 +09:00
parent 7244dda20f
commit 5318d37462
1 changed files with 2 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
README.md
View File

@@ -1158,11 +1158,10 @@ Additionally the following `repmgrd` options must be set in `repmgr.conf`:
promote_command='repmgr standby promote -f /etc/repmgr.conf --log-to-file' promote_command='repmgr standby promote -f /etc/repmgr.conf --log-to-file'
follow_command='repmgr standby follow -f /etc/repmgr.conf --log-to-file' follow_command='repmgr standby follow -f /etc/repmgr.conf --log-to-file'
Note that the `--log-to-file` option will cause `repmgr` output to be logged to Note that the `--log-to-file` option will cause `repmgr`'s output to be logged to
the destination configured to receive log output `repmgrd`. the destination configured to receive log output for `repmgrd`.
See `repmgr.conf.sample` for further `repmgrd`-specific settings See `repmgr.conf.sample` for further `repmgrd`-specific settings
When `failover` is set to `automatic`, upon detecting failure of the current When `failover` is set to `automatic`, upon detecting failure of the current
master, `repmgrd` will execute one of `promote_command` or `follow_command`, master, `repmgrd` will execute one of `promote_command` or `follow_command`,
depending on whether the current server is becoming the new master or depending on whether the current server is becoming the new master or