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 README

Browse Source
This commit is contained in:
Ian Barwick
2017-09-22 15:27:17 +09:00
parent 95cc403efb
commit fcae08f5a8
1 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
README.md
View File

@@ -805,12 +805,12 @@ meaning replication changes "cascade" down through a hierarchy of servers. This
can be used to reduce load on the primary and minimize bandwidth usage between
sites.
`repmgr` supports cascading replication. When cloning a standby, in `repmgr.conf`
set the command-line parameter `--upstream-node-id` to the `node_id` of the
server the standby should connect to, and `repmgr` will perform the clone using
this server and create `recovery.conf` to point to it. Note that if `--upstream-node-id`
is not explicitly provided, `repmgr` will set the standby's `recovery.conf` to
point to the primary node.
`repmgr` supports cascading replication. When cloning a standby, set the
command-line parameter `--upstream-node-id` to the `node_id` of the
server the standby should connect to, and `repmgr` will create `recovery.conf`
pointing to this server. Note that if `--upstream-node-id` is not explicitly
provided, `repmgr` will set the standby's `recovery.conf` to point to the primary
node.
To demonstrate cascading replication, ensure you have a primary and standby
set up as shown above in the section "Setting up a simple replication cluster