Update PITR setence to mention WAL and file system dump.

diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html
index ee083875e2804060bc85eb256fe5ed7ef67ba355..3935649b043ba0ec20ccc278e006ff5a84a3f7b7 100644 (file)
--- a/doc/src/FAQ/TODO.html
+++ b/doc/src/FAQ/TODO.html
@@ -8,7 +8,7 @@
 
 PostgreSQL TODO List
 Current maintainer:     Bruce Momjian ([email protected])
-Last updated:           Mon Apr 18 10:42:34 EDT 2005
+Last updated:           Mon Apr 18 11:03:14 EDT 2005
 
 The most recent version of this document can be viewed at the PostgreSQL web
 site, http://www.PostgreSQL.org.
@@ -103,10 +103,10 @@ first.
   logs
   Currently only full WAL files are archived. This means that the most
   recent transactions aren't available for recovery in case of a disk
-  failure.
+  failure.  This could be triggered by a user command or a timer.
 
-  Force archiving of partially-full WAL files when pg_stop_backup() is
-  called or the server is stopped
+  Automatically force archiving of partially-filled WAL files when 
+  pg_stop_backup() is called or the server is stopped
   Doing this will allow administrators to know more easily when the
   archive contins all the files needed for point-in-time recovery.
 

diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml
index 1a5d1c66c32d376dbfdeffac127537661f875817..65cb4c62970863bfef52cb6f995a7d0bd55a6604 100644 (file)
--- a/doc/src/sgml/backup.sgml
+++ b/doc/src/sgml/backup.sgml
@@ -1,5 +1,5 @@
 
 
  Backup and Restore
@@ -741,10 +741,10 @@ SELECT pg_stop_backup();
     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 pg_stop_backup and the archiving of
     all WAL segment files needed to make the file system backup
     consistent.