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

Update documentation/sample configuration with references to --wal-method

Browse Source
This commit is contained in:
Ian Barwick
2017-02-16 10:13:59 +09:00
parent 5391a8a6a3
commit f7af020ff3
2 changed files with 11 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
README.md
View File

@@ -333,10 +333,11 @@ The following replication settings may need to be adjusted:
archive_command = '/bin/true' archive_command = '/bin/true'
# If cloning using rsync, or you have configured `pg_basebackup_options` # If cloning using rsync, or you have configured `pg_basebackup_options`
# in `repmgr.conf` to include the setting `--xlog-method=fetch`, *and* # in `repmgr.conf` to include the setting `--xlog-method=fetch` (from
# you have not set `restore_command` in `repmgr.conf`to fetch WAL files # PostgreSQL 10 `--wal-method=fetch`), *and* you have not set
# from another source such as Barman, you'll need to set `wal_keep_segments` # `restore_command` in `repmgr.conf`to fetch WAL files from another
# to a high enough value to ensure that all WAL files generated while # source such as Barman, you'll need to set `wal_keep_segments` to a
# high enough value to ensure that all WAL files generated while
# the standby is being cloned are retained until the standby starts up. # the standby is being cloned are retained until the standby starts up.
# wal_keep_segments = 5000 # wal_keep_segments = 5000
@@ -501,7 +502,8 @@ place. To ensure this happens when using the default `pg_basebackup` method,
`repmgr` will set `pg_basebackup`'s `--xlog-method` parameter to `stream`, `repmgr` will set `pg_basebackup`'s `--xlog-method` parameter to `stream`,
which will ensure all WAL files generated during the cloning process are which will ensure all WAL files generated during the cloning process are
streamed in parallel with the main backup. Note that this requires two streamed in parallel with the main backup. Note that this requires two
replication connections to be available. replication connections to be available (`repmgr` will verify sufficient
connections are available before attempting to clonse).
To override this behaviour, in `repmgr.conf` set `pg_basebackup`'s To override this behaviour, in `repmgr.conf` set `pg_basebackup`'s
`--xlog-method` parameter to `fetch`: `--xlog-method` parameter to `fetch`:
@@ -513,6 +515,9 @@ See the `pg_basebackup` documentation for details:
https://www.postgresql.org/docs/current/static/app-pgbasebackup.html https://www.postgresql.org/docs/current/static/app-pgbasebackup.html
> *NOTE*: From PostgreSQL 10, `pg_basebackup`'s `--xlog-method` parameter
> has been renamed to `--wal-method`.
Make any adjustments to the standby's PostgreSQL configuration files now, Make any adjustments to the standby's PostgreSQL configuration files now,
then start the server. then start the server.

2
repmgr.conf.sample
View File

@@ -143,7 +143,7 @@
# external command arguments. Values shown are examples. # external command arguments. Values shown are examples.
#pg_ctl_options='-s' #pg_ctl_options='-s'
#pg_basebackup_options='--xlog-method=s' #pg_basebackup_options='--label=repmgr_backup'
# This is the host name of the barman server, which is used for connecting over # This is the host name of the barman server, which is used for connecting over
# to the barman server (passwordless ssh keys should be in place) # to the barman server (passwordless ssh keys should be in place)