Update walcontrol item:

< * Allow control over which tables are WAL-logged
> * Allow control over which tables are WAL-logged [walcontrol]
1038c1038,1039
<   stable logging probably can not have indexes.  [walcontrol]
>   stable logging probably can not have indexes.  One complexity is
>   the handling of indexes on TOAST tables.

diff --git a/doc/TODO b/doc/TODO
index 62b5f2ff7d9f9f855662c4c7a939e2e5cefa57e2..d7e210651fc46aa7639d79396430235f410ee230 100644 (file)
--- a/doc/TODO
+++ b/doc/TODO
@@ -2,7 +2,7 @@
 PostgreSQL TODO List
 ====================
 Current maintainer:    Bruce Momjian ([email protected])
-Last updated:      Wed Feb  1 12:32:41 EST 2006
+Last updated:      Fri Feb  3 22:23:19 EST 2006
 
 The most recent version of this document can be viewed at
 http://www.postgresql.org/docs/faqs.TODO.html.
@@ -1024,7 +1024,7 @@ Write-Ahead Log
   remove the 'fsync' parameter (which results in an an inconsistent
   database) in favor of this capability.
 
-* Allow control over which tables are WAL-logged
+* Allow control over which tables are WAL-logged [walcontrol]
 
   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
@@ -1035,7 +1035,8 @@ Write-Ahead Log
   using ALTER TABLE, e.g. ALTER TABLE PERSISTENCE [ DROP | TRUNCATE | 
   STABLE | DEFAULT ].  Tables using non-default logging should not use
   referential integrity with default-logging tables, and tables using
-  stable logging probably can not have indexes.  [walcontrol]
+  stable logging probably can not have indexes.  One complexity is
+  the handling of indexes on TOAST tables.
 
 
 Optimizer / Executor

diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html
index 67628148c88b94e237d63902ad570b8970d63821..9aafe3e9c305aa7faf81adc076b02eab67c04eaf 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 Feb  1 12:32:41 EST 2006
+Last updated:           Fri Feb  3 22:23:19 EST 2006
 
 The most recent version of this document can be viewed at
 http://www.postgresql.org/docs/faqs.TODO.html.
@@ -928,7 +928,7 @@ first.
   remove the 'fsync' parameter (which results in an an inconsistent
   database) in favor of this capability.
 
-  Allow control over which tables are WAL-logged
+  Allow control over which tables are WAL-logged [walcontrol]
   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
@@ -938,7 +938,8 @@ first.
   using ALTER TABLE, e.g. ALTER TABLE PERSISTENCE [ DROP | TRUNCATE | 
   STABLE | DEFAULT ].  Tables using non-default logging should not use
   referential integrity with default-logging tables, and tables using
-  stable logging probably can not have indexes.  [walcontrol]
+  stable logging probably can not have indexes.  One complexity is
+  the handling of indexes on TOAST tables.
 
 
 Optimizer / Executor