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

FAQ fixes and updates

Browse Source
This commit is contained in:
Ian Barwick
2015-03-26 11:07:18 +09:00
parent 3e621f43d1
commit eabe618738
2 changed files with 7 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
FAQ.md
View File

@@ -52,6 +52,12 @@ General
- How can a failed master be re-added as a standby? - How can a failed master be re-added as a standby?
This is a two-stage process. First, the failed master's data directory
must be re-synced with the current master; secondly the failed master
needs to be re-registered as a standby. The section "Converting a failed
master to a standby" in the `README.md` file contains more detailed
information on this process.
- Is there an easy way to check my master server is correctly configured - Is there an easy way to check my master server is correctly configured
for use with `repmgr`? for use with `repmgr`?
@@ -80,7 +86,7 @@ General
with the same file from the master, specify the files in the with the same file from the master, specify the files in the
`rsync_options` configuration option, e.g. `rsync_options` configuration option, e.g.
rsync_options=--exclude=postgresql.local.conf rsync_options=--exclude=postgresql.local.conf
This option is only available when using the `--rsync-only` option. This option is only available when using the `--rsync-only` option.

1
README.md
View File

@@ -352,7 +352,6 @@ Following event types currently exist:
repmgrd_failover_follow repmgrd_failover_follow
Cascading replication Cascading replication
--------------------- ---------------------