diff options
Diffstat (limited to 'doc/src')
| -rw-r--r-- | doc/src/sgml/high-availability.sgml | 5 | ||||
| -rw-r--r-- | doc/src/sgml/recovery-config.sgml | 4 |
2 files changed, 7 insertions, 2 deletions
diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml index e33d3151375..b97167fc50b 100644 --- a/doc/src/sgml/high-availability.sgml +++ b/doc/src/sgml/high-availability.sgml @@ -660,7 +660,10 @@ protocol to make nodes agree on a serializable transactional order. command file <filename>recovery.conf</> in the standby's cluster data directory, and turn on <varname>standby_mode</>. Set <varname>restore_command</> to a simple command to copy files from - the WAL archive. + the WAL archive. If you plan to have multiple standby servers for high + availability purposes, set <varname>recovery_target_timeline</> to + <literal>latest</>, to make the standby server follow the timeline change + that occurs at failover to another standby. </para> <note> diff --git a/doc/src/sgml/recovery-config.sgml b/doc/src/sgml/recovery-config.sgml index 602fbe2c76e..e9e95acb8dc 100644 --- a/doc/src/sgml/recovery-config.sgml +++ b/doc/src/sgml/recovery-config.sgml @@ -240,7 +240,9 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows <para> Specifies recovering into a particular timeline. The default is to recover along the same timeline that was current when the - base backup was taken. You only need to set this parameter + base backup was taken. Setting this to <literal>latest</> recovers + to the latest timeline found in the archive, which is useful in + a standby server. Other than that you only need to set this parameter in complex re-recovery situations, where you need to return to a state that itself was reached after a point-in-time recovery. See <xref linkend="backup-timelines"> for discussion. |