database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-30 11:03:19 +03:00
Code Activity

If recovery_target_timeline is set to 'latest' and standby mode is enabled,

Browse Source 
periodically rescan the archive for new timelines, while waiting for new WAL
segments to arrive. This allows you to set up a standby server that follows
the TLI change if another standby server is promoted to master. Before this,
you had to restart the standby server to make it notice the new timeline.

This patch only scans the archive for TLI changes, it won't follow a TLI
change in streaming replication. That is much needed too, but it would be a
much bigger patch than I dare to sneak in this late in the release cycle.

There was discussion on improving the sanity checking of the WAL segments so
that the system would notice more reliably if the new timeline isn't an
ancestor of the current one, but that is not included in this patch.

Reviewed by Fujii Masao.
This commit is contained in:
Heikki Linnakangas
2011-03-07 21:02:40 +02:00
parent bcf85e3f44
commit 1a4ab9ec23
3 changed files with 83 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
doc/src/sgml/high-availability.sgml
View File

@ -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>

4
doc/src/sgml/recovery-config.sgml
View File

@ -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.