Update wording:

<   the table. Another option is to avoid transaction logging entirely
<   and truncate or drop the table on crash recovery.  These should be
<   implemented using ALTER TABLE, e.g. ALTER TABLE PERSISTENCE [ DROP |
<   TRUNCATE | STABLE | DEFAULT ].  [wallog]
>   the table.  This would affect COPY, and perhaps INSERT/UPDATE too.
>   Another option is to avoid transaction logging entirely and truncate
>   or drop the table on crash recovery.  These should be implemented
>   using ALTER TABLE, e.g. ALTER TABLE PERSISTENCE [ DROP | TRUNCATE |
>   STABLE | DEFAULT ].  [wallog]

diff --git a/doc/TODO b/doc/TODO
index dc7c97ffbc738f870377f0c9d60b0de2a1abd7a9..0c0bf9e61fde706bab08d1e4f56c7a32b4ffbebe 100644 (file)
--- a/doc/TODO
+++ b/doc/TODO
@@ -2,7 +2,7 @@
 PostgreSQL TODO List
 ====================
 Current maintainer:    Bruce Momjian ([email protected])
-Last updated:      Thu Jan  5 11:23:42 EST 2006
+Last updated:      Thu Jan  5 11:26:44 EST 2006
 
 The most recent version of this document can be viewed at
 http://www.postgresql.org/docs/faqs.TODO.html.
@@ -1019,10 +1019,11 @@ Write-Ahead Log
   Allow tables to bypass WAL writes and just fsync() dirty pages on
   commit.  To do this, only a single writer can modify the table, and
   writes must happen only on new pages.  Readers can continue accessing
-  the table. Another option is to avoid transaction logging entirely 
-  and truncate or drop the table on crash recovery.  These should be 
-  implemented using ALTER TABLE, e.g. ALTER TABLE PERSISTENCE [ DROP |
-  TRUNCATE | STABLE | DEFAULT ].  [wallog]
+  the table.  This would affect COPY, and perhaps INSERT/UPDATE too.
+  Another option is to avoid transaction logging entirely and truncate 
+  or drop the table on crash recovery.  These should be implemented 
+  using ALTER TABLE, e.g. ALTER TABLE PERSISTENCE [ DROP | TRUNCATE | 
+  STABLE | DEFAULT ].  [wallog]
 
 
 Optimizer / Executor

diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html
index 0cbe43fb1d2b619b7cee26024bdc26e2546ced9f..8b2f9541586467bb95166a2129ea29ddae14993d 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:           Thu Jan  5 11:23:42 EST 2006
+Last updated:           Thu Jan  5 11:26:44 EST 2006
 
 The most recent version of this document can be viewed at
 http://www.postgresql.org/docs/faqs.TODO.html.
@@ -923,10 +923,11 @@ first.
   Allow tables to bypass WAL writes and just fsync() dirty pages on
   commit.  To do this, only a single writer can modify the table, and
   writes must happen only on new pages.  Readers can continue accessing
-  the table. Another option is to avoid transaction logging entirely 
-  and truncate or drop the table on crash recovery.  These should be 
-  implemented using ALTER TABLE, e.g. ALTER TABLE PERSISTENCE [ DROP |
-  TRUNCATE | STABLE | DEFAULT ].  [wallog]
+  the table.  This would affect COPY, and perhaps INSERT/UPDATE too.
+  Another option is to avoid transaction logging entirely and truncate 
+  or drop the table on crash recovery.  These should be implemented 
+  using ALTER TABLE, e.g. ALTER TABLE PERSISTENCE [ DROP | TRUNCATE | 
+  STABLE | DEFAULT ].  [wallog]
 
 
 Optimizer / Executor