From 01979d1bd52dac4f3c37a648019b4e4564cb791e Mon Sep 17 00:00:00 2001
From: Bruce Momjian
Date: Mon, 18 Apr 2005 17:40:40 +0000
Subject: Update PITR setence to mention WAL and file system dump.

---
 doc/src/sgml/backup.sgml | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

(limited to 'doc/src/sgml')

diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml
index 1a5d1c66c32..65cb4c62970 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.63 2005/04/18 13:11:04 momjian Exp $
+$PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.64 2005/04/18 17:40:40 momjian Exp $
 -->
 <chapter id="backup">
  <title>Backup and Restore</title>
@@ -741,10 +741,10 @@ SELECT pg_stop_backup();
     <literal>0000000100001234000055CD.007C9330.backup</>. (The second
     number in the file name stands for an exact position within the WAL
     file, and can ordinarily be ignored.) Once you have safely archived
-    the WAL segment files used during the file system backup (as
-    specified in the backup history file), you can delete all archived
-    WAL segments with names numerically less. Keep in mind that only
-    completed WAL segment files are archived, so there will be delay
+    the file system backup and the WAL segment files used during the 
+    backup (as specified in the backup history file), you can delete all 
+    archived WAL segments with names numerically less. Keep in mind that 
+    only completed WAL segment files are archived, so there will be delay
     between running <function>pg_stop_backup</> and the archiving of
     all WAL segment files needed to make the file system backup
     consistent.
-- 
cgit v1.2.3