aboutsummaryrefslogtreecommitdiff
path: root/doc/src/sgml/backup.sgml
diff options
context:
space:
mode:
Diffstat (limited to 'doc/src/sgml/backup.sgml')
-rw-r--r--doc/src/sgml/backup.sgml11
1 files changed, 10 insertions, 1 deletions
diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml
index be05a332050..8cb24d6ae54 100644
--- a/doc/src/sgml/backup.sgml
+++ b/doc/src/sgml/backup.sgml
@@ -1309,7 +1309,16 @@ restore_command = 'cp /mnt/server/archivedir/%f %p'
a new timeline is created to identify the series of WAL records
generated after that recovery. The timeline
ID number is part of WAL segment file names so a new timeline does
- not overwrite the WAL data generated by previous timelines. It is
+ not overwrite the WAL data generated by previous timelines.
+ For example, in the WAL file name
+ <filename>0000000100001234000055CD</filename>, the leading
+ <literal>00000001</literal> is the timeline ID in hexadecimal. (Note that
+ in other contexts, such as server log messages, timeline IDs are
+ usually printed in decimal.)
+ </para>
+
+ <para>
+ It is
in fact possible to archive many different timelines. While that might
seem like a useless feature, it's often a lifesaver. Consider the
situation where you aren't quite sure what point-in-time to recover to,