From eb8f9cc066dd0c9642a6101a833b6e0d698c2a6b Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Fri, 24 Feb 2006 14:03:01 +0000
Subject: [PATCH] Mention that the archive history file has the wal start/stop
file names.
---
doc/src/sgml/backup.sgml | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml
index 2341105a353..9245c6278b6 100644
--- a/doc/src/sgml/backup.sgml
+++ b/doc/src/sgml/backup.sgml
@@ -1,5 +1,5 @@
<!--
-$PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.76 2005/11/07 17:36:44 tgl Exp $
+$PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.77 2006/02/24 14:03:01 momjian Exp $
-->
<chapter id="backup">
<title>Backup and Restore</title>
@@ -744,12 +744,13 @@ SELECT pg_stop_backup();
<function>pg_stop_backup</> and the archiving of all WAL segment
files needed to make the file system backup consistent.
</para>
+
<para>
The backup history file is just a small text file. It contains the
label string you gave to <function>pg_start_backup</>, as well as
- the starting and ending times of the backup. If you used the label
- to identify where the associated dump file is kept, then the
- archived history file is enough to tell you which dump file to
+ the starting and ending times and WAL segments of the backup.
+ If you used the label to identify where the associated dump file is kept,
+ then the archived history file is enough to tell you which dump file to
restore, should you need to do so.
</para>
--
GitLab