Done:

< 	  o Add command to archive partially filled write-ahead logs? [pitr]
<
< 	    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.
<

Reorder:

< 	  o %Create dump tool for write-ahead logs for use in determining
< 	    transaction id for point-in-time recovery
> 	  o %Create dump tool for write-ahead logs for use in determining
> 	    transaction id for point-in-time recovery

diff --git a/doc/TODO b/doc/TODO
index b8bede9dacffa4da52e14dba09faf343c158a1a7..f43d747371edb9fdc0a0b8d456c3b9f075e0ee2d 100644 (file)
--- a/doc/TODO
+++ b/doc/TODO
@@ -2,7 +2,7 @@
 PostgreSQL TODO List
 ====================
 Current maintainer:    Bruce Momjian ([email protected])
-Last updated:      Wed Sep 20 19:01:42 EDT 2006
+Last updated:      Tue Sep 26 07:18:13 EDT 2006
 
 The most recent version of this document can be viewed at
 http://www.postgresql.org/docs/faqs.TODO.html.
@@ -139,19 +139,13 @@ Administration
 
 * Point-In-Time Recovery (PITR)
 
-     o Add command to archive partially filled write-ahead logs? [pitr]
-
-       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.
-
-     o %Create dump tool for write-ahead logs for use in determining
-       transaction id for point-in-time recovery
      o Allow a warm standby system to also allow read-only statements
        [pitr]
 
        This is useful for checking PITR recovery.
 
+     o %Create dump tool for write-ahead logs for use in determining
+       transaction id for point-in-time recovery
      o Allow the PITR process to be debugged and data examined
 
 

diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html
index 5f7754cc01559cacc9e19719422c4cbb7a8e3bbe..b4a5c37f79b35d14eab5d9f8c39086335b41496b 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:           Wed Sep 20 19:01:42 EDT 2006
+Last updated:           Tue Sep 26 07:18:13 EDT 2006
 
 The most recent version of this document can be viewed at
 http://www.postgresql.org/docs/faqs.TODO.html.
@@ -127,17 +127,12 @@ first.
   
   Point-In-Time Recovery (PITR)
   
-    Add command to archive partially filled write-ahead logs? [pitr]
-            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.
-
-    %Create dump tool for write-ahead logs for use in determining
-            transaction id for point-in-time recovery
-    Allow a warm standby system to also allow read-only statements
+    Allow a warm standby system to also allow read-only statements
             [pitr]
             This is useful for checking PITR recovery.
 
+    %Create dump tool for write-ahead logs for use in determining
+            transaction id for point-in-time recovery
     Allow the PITR process to be debugged and data examined