Update pg_dump item:

< 	  produce a single dump output file.
> 	  produce a single dump output file.  It also would require
> 	  several sessions to share the same snapshot.

diff --git a/doc/TODO b/doc/TODO
index 492e48e5f625605a6d5baba658e5d31ad1101eab..b9b8555ae3df5556aca6a175458880398c6c2f79 100644 (file)
--- a/doc/TODO
+++ b/doc/TODO
@@ -1,7 +1,7 @@
 PostgreSQL TODO List
 ====================
 Current maintainer:    Bruce Momjian ([email protected])
-Last updated:      Mon Mar  3 21:48:18 EST 2008
+Last updated:      Tue Mar  4 09:38:30 EST 2008
 
 The most recent version of this document can be viewed at
 http://www.postgresql.org/docs/faqs.TODO.html.
@@ -842,7 +842,8 @@ Clients
      multiple objects simultaneously
 
      The difficulty with this is getting multiple dump processes to
-     produce a single dump output file.
+     produce a single dump output file.  It also would require
+     several sessions to share the same snapshot.
      http://archives.postgresql.org/pgsql-hackers/2008-02/msg00205.php
 
    o Allow pg_restore to utilize multiple CPUs and I/O channels by

diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html
index dcadc3847ba46d7fc555335a21640df435955336..cb87f75f61540091249e00e5742c6ad574bf335a 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 Mar  3 21:48:18 EST 2008
+Last updated:           Tue Mar  4 09:38:30 EST 2008
 
 The most recent version of this document can be viewed at
 http://www.postgresql.org/docs/faqs.TODO.html.
@@ -750,7 +750,8 @@ first.  There is also a developer's wiki at
     Allow pg_dump to utilize multiple CPUs and I/O channels by dumping
           multiple objects simultaneously
           The difficulty with this is getting multiple dump processes to
-          produce a single dump output file.
+          produce a single dump output file.  It also would require
+          several sessions to share the same snapshot.
           http://archives.postgresql.org/pgsql-hackers/2008-02/msg00205.php
 
     Allow pg_restore to utilize multiple CPUs and I/O channels by