diff options
| author | Peter Eisentraut <peter@eisentraut.org> | 2019-01-11 10:36:10 +0100 |
|---|---|---|
| committer | Peter Eisentraut <peter@eisentraut.org> | 2019-01-13 10:01:05 +0100 |
| commit | 0acb3bc33af11a57d560cbce5a74246eb3e642db (patch) | |
| tree | 1745226472594f81ff53e720b522c224f08984ac /doc/src | |
| parent | 373bda61d2d620e704815553978726c9be9e1209 (diff) | |
| download | postgresql-0acb3bc33af11a57d560cbce5a74246eb3e642db.tar.gz postgresql-0acb3bc33af11a57d560cbce5a74246eb3e642db.zip | |
Change default of recovery_target_timeline to 'latest'
This is what one usually wants for recovery and almost always wants
for a standby.
Discussion: https://www.postgresql.org/message-id/flat/6dd2c23a-4162-8469-410f-bfe146e28c0c@2ndquadrant.com/
Reviewed-by: David Steele <david@pgmasters.net>
Reviewed-by: Michael Paquier <michael@paquier.xyz>
Diffstat (limited to 'doc/src')
| -rw-r--r-- | doc/src/sgml/config.sgml | 8 | ||||
| -rw-r--r-- | doc/src/sgml/high-availability.sgml | 6 |
2 files changed, 9 insertions, 5 deletions
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index f64402adbe1..b6f5822b847 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -3353,10 +3353,14 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows Specifies recovering into a particular timeline. The value can be a numeric timeline ID or a special value. The value <literal>current</literal> recovers along the same timeline that was - current when the base backup was taken. That is the default. The + current when the base backup was taken. The value <literal>latest</literal> 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 + a standby server. <literal>latest</literal> is the default. + </para> + + <para> + You usually 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. diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml index d8fd195da09..4882b20828a 100644 --- a/doc/src/sgml/high-availability.sgml +++ b/doc/src/sgml/high-availability.sgml @@ -690,8 +690,8 @@ protocol to make nodes agree on a serializable transactional order. <filename>standby.signal</filename> in the standby's cluster data directory. Set <xref linkend="guc-restore-command"/> to a simple command to copy files from the WAL archive. If you plan to have multiple standby servers for high - availability purposes, set <varname>recovery_target_timeline</varname> to - <literal>latest</literal>, to make the standby server follow the timeline change + availability purposes, make sure that <varname>recovery_target_timeline</varname> is set to + <literal>latest</literal> (the default), to make the standby server follow the timeline change that occurs at failover to another standby. </para> @@ -1024,7 +1024,7 @@ primary_slot_name = 'node_a_slot' <para> If an upstream standby server is promoted to become new master, downstream servers will continue to stream from the new master if - <varname>recovery_target_timeline</varname> is set to <literal>'latest'</literal>. + <varname>recovery_target_timeline</varname> is set to <literal>'latest'</literal> (the default). </para> <para> |