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

README and "repmgr standby --help" updates

Browse Source
This commit is contained in:
Ian Barwick
2017-09-06 14:13:06 +09:00
parent a28bbd68eb
commit 66219c3097
2 changed files with 6 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@@ -774,11 +774,11 @@ can be used to reduce load on the primary and minimize bandwith usage between
sites. sites.
`repmgr` supports cascading replication. When cloning a standby, in `repmgr.conf` `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 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 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` this server and create `recovery.conf` to point to it. Note that if `--upstream-node-id`
is not explicitly provided, `repmgr` will use the primary as the server is not explicitly provided, `repmgr` will set the standby's `recovery.conf` to
to clone from and attach to. point to the primary node.
To demonstrate cascading replication, ensure you have a primary and standby 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 set up as shown above in the section "Setting up a simple replication cluster

5
repmgr-action-standby.c
View File

@@ -4985,10 +4985,11 @@ do_standby_help(void)
" PostgreSQL data directory\n")); " PostgreSQL data directory\n"));
printf(_(" --dry-run perform checks but don't actually clone the standby\n")); printf(_(" --dry-run perform checks but don't actually clone the standby\n"));
printf(_(" --no-upstream-connection when using Barman, do not connect to upstream node\n")); printf(_(" --no-upstream-connection when using Barman, do not connect to upstream node\n"));
printf(_(" --upstream-conninfo \"primary_conninfo\" value to write in recovery.conf\n" \
" when the intended upstream server does not yet exist\n"));
printf(_(" -R, --remote-user=USERNAME database server username for SSH operations (default: \"%s\")\n"), runtime_options.username); printf(_(" -R, --remote-user=USERNAME database server username for SSH operations (default: \"%s\")\n"), runtime_options.username);
printf(_(" --replication-user user to make replication connections with (optional, not usually required)\n")); printf(_(" --replication-user user to make replication connections with (optional, not usually required)\n"));
printf(_(" --upstream-conninfo \"primary_conninfo\" value to write in recovery.conf\n" \
" when the intended upstream server does not yet exist\n"));
printf(_(" --upstream-node-id ID of the upstream node to replicate from (optional, defaults to primary node)\n"));
printf(_(" --without-barman do not use Barman even if configured\n")); printf(_(" --without-barman do not use Barman even if configured\n"));
puts(""); puts("");