Update PITR:

< 	    write-ahead logs [pitr]
> 	    write-ahead logs? [pitr]
< 	    recovery.
> 	    recovery.  A function call to do this would also be useful.

diff --git a/doc/TODO b/doc/TODO
index 5193b155a3e59adf86087335ed990f754cada22e..85ccd90af83c09a097bf28e4d9edc736db583b08 100644 (file)
--- a/doc/TODO
+++ b/doc/TODO
@@ -2,7 +2,7 @@
 PostgreSQL TODO List
 ====================
 Current maintainer:    Bruce Momjian ([email protected])
-Last updated:      Tue Jul 25 00:11:20 EDT 2006
+Last updated:      Tue Jul 25 11:21:42 EDT 2006
 
 The most recent version of this document can be viewed at
 http://www.postgresql.org/docs/faqs.TODO.html.
@@ -145,7 +145,7 @@ Administration
 * Point-In-Time Recovery (PITR)
 
      o Allow point-in-time recovery to archive partially filled
-       write-ahead logs [pitr]
+       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
@@ -157,7 +157,7 @@ Administration
 
        Doing this will allow administrators to know more easily when
        the archive contains all the files needed for point-in-time
-       recovery.  
+       recovery.  A function call to do this would also be useful.
        http://archives.postgresql.org/pgsql-patches/2005-04/msg00121.php
 
      o %Create dump tool for write-ahead logs for use in determining

diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html
index 9ddd24a2f783b85d6e4f88f5a5c2f864e1d7d3d9..f5d4489f4c8417a0a5c913a642e3e687ee702557 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:           Tue Jul 25 00:11:20 EDT 2006
+Last updated:           Tue Jul 25 11:21:42 EDT 2006
 
 The most recent version of this document can be viewed at
 http://www.postgresql.org/docs/faqs.TODO.html.
@@ -132,7 +132,7 @@ first.
   Point-In-Time Recovery (PITR)
   
     Allow point-in-time recovery to archive partially filled
-            write-ahead logs [pitr]
+            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. This could be triggered by a user command or
@@ -142,7 +142,7 @@ first.
             pg_stop_backup() is called or the server is stopped
             Doing this will allow administrators to know more easily when
             the archive contains all the files needed for point-in-time
-            recovery.  
+            recovery.  A function call to do this would also be useful.
             http://archives.postgresql.org/pgsql-patches/2005-04/msg00121.php
 
     %Create dump tool for write-ahead logs for use in determining