Update:

> 	o Allow COPY on a newly-created table to skip WAL logging
450a452,456
> 	  On crash recovery, the table involved in the COPY would
> 	  have its heap and index files truncated.  One issue is
> 	  that no other backend should be able to add to the table
> 	  at the same time, which is something that is currently
> 	  allowed.

diff --git a/doc/TODO b/doc/TODO
index 2e0cd8a80505b15c118ee080436d75034f8acf77..f7026afe22e0a9ade839d216418acd7fcbf5b308 100644 (file)
--- a/doc/TODO
+++ b/doc/TODO
@@ -2,7 +2,7 @@
 PostgreSQL TODO List
 ====================
 Current maintainer:    Bruce Momjian ([email protected])
-Last updated:      Fri Sep  2 17:01:18 EDT 2005
+Last updated:      Fri Sep  2 17:10:58 EDT 2005
 
 The most recent version of this document can be viewed at
 http://www.postgresql.org/docs/faqs.TODO.html.
@@ -389,7 +389,6 @@ SQL Commands
      copy of db?
 
    o Add ON COMMIT capability to CREATE TABLE AS ... SELECT
-   o Allow COPY into an new table to skip WAL logging
 
 
 * UPDATE
@@ -448,7 +447,13 @@ SQL Commands
      processed, with ROLLBACK on COPY failure.
 
    o %Have COPY return the number of rows loaded/unloaded?
+   o Allow COPY on a newly-created table to skip WAL logging
 
+     On crash recovery, the table involved in the COPY would
+     have its heap and index files truncated.  One issue is
+     that no other backend should be able to add to the table
+     at the same time, which is something that is currently
+     allowed.
 
 * GRANT/REVOKE
 

diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html
index 0b7aa3cef5cbf515374ccc6e8d2353c450349675..9fd764ee637f3e4f1b7c47f53754f17b51eb4ab9 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:           Fri Sep  2 17:01:18 EDT 2005
+Last updated:           Fri Sep  2 17:10:58 EDT 2005
 
 The most recent version of this document can be viewed at
 http://www.postgresql.org/docs/faqs.TODO.html.
@@ -355,7 +355,6 @@ first.
     Use more reliable method for CREATE DATABASE to get a consistent
           copy of db?
     Add ON COMMIT capability to CREATE TABLE AS ... SELECT
-    Allow COPY into an new table to skip WAL logging
   
   UPDATE
   
@@ -407,6 +406,13 @@ first.
           processed, with ROLLBACK on COPY failure.
 
     %Have COPY return the number of rows loaded/unloaded?
+    Allow COPY on a newly-created table to skip WAL logging
+          On crash recovery, the table involved in the COPY would
+          have its heap and index files truncated.  One issue is
+          that no other backend should be able to add to the table
+          at the same time, which is something that is currently
+          allowed.
+
   
   GRANT/REVOKE