Done:

< * Allow buffered WAL writes and fsync

diff --git a/doc/TODO b/doc/TODO
index b3b526011aa67a51c611bb5f1c7f9e27f0a31028..deffc49ac08e4147d9dfdf978a568e865df77420 100644 (file)
--- a/doc/TODO
+++ b/doc/TODO
@@ -1,7 +1,7 @@
 PostgreSQL TODO List
 ====================
 Current maintainer:    Bruce Momjian ([email protected])
-Last updated:      Tue Jul 17 20:15:52 EDT 2007
+Last updated:      Wed Aug  1 19:13:20 EDT 2007
 
 The most recent version of this document can be viewed at
 http://www.postgresql.org/docs/faqs.TODO.html.
@@ -1330,15 +1330,7 @@ Write-Ahead Log
   rotation to fsync again. One idea is to write the WAL to different
   offsets that might reduce the rotational delay.
 
-* Allow buffered WAL writes and fsync
-
-  Instead of guaranteeing recovery of all committed transactions, this
-  would provide improved performance by delaying WAL writes and fsync
-  so an abrupt operating system restart might lose a few seconds of
-  committed transactions but still be consistent.  We could perhaps
-  remove the 'fsync' parameter (which results in an an inconsistent
-  database) in favor of this capability.
-
+* -Allow buffered WAL writes and fsync
 * Allow WAL logging to be turned off for a table, but the table
   might be dropped or truncated during crash recovery [walcontrol]
 

diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html
index d8805855a1e122e607a307eaf82ca60642a2a7bf..4c3615b6c9b5c4570d9545694e99e08ca5b1b476 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 17 20:15:52 EDT 2007
+Last updated:           Wed Aug  1 19:13:20 EDT 2007
 
 The most recent version of this document can be viewed at
 http://www.postgresql.org/docs/faqs.TODO.html.
@@ -1182,14 +1182,7 @@ first.  There is also a developer's wiki at
   rotation to fsync again. One idea is to write the WAL to different
   offsets that might reduce the rotational delay.
 
-  Allow buffered WAL writes and fsync
-  Instead of guaranteeing recovery of all committed transactions, this
-  would provide improved performance by delaying WAL writes and fsync
-  so an abrupt operating system restart might lose a few seconds of
-  committed transactions but still be consistent.  We could perhaps
-  remove the 'fsync' parameter (which results in an an inconsistent
-  database) in favor of this capability.
-
+  -Allow buffered WAL writes and fsync
   Allow WAL logging to be turned off for a table, but the table
   might be dropped or truncated during crash recovery [walcontrol]
   Allow tables to bypass WAL writes and just fsync() dirty pages on