diff --git a/doc/TODO b/doc/TODO index 08d85bfa9da..8eacdd6f1f9 100644 --- a/doc/TODO +++ b/doc/TODO @@ -1,7 +1,7 @@ PostgreSQL TODO List ==================== Current maintainer: Bruce Momjian (bruce@momjian.us) -Last updated: Sat Apr 19 08:15:19 EDT 2008 +Last updated: Sat Apr 19 08:32:51 EDT 2008 The most recent version of this document can be viewed at http://www.postgresql.org/docs/faqs.TODO.html. diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html index 06aa4e11476..9ceb4ad544a 100644 --- a/doc/src/FAQ/TODO.html +++ b/doc/src/FAQ/TODO.html @@ -8,7 +8,7 @@
Current maintainer: Bruce Momjian (bruce@momjian.us)
-Last updated: Sat Apr 19 08:15:19 EDT 2008
+Last updated: Sat Apr 19 08:32:51 EDT 2008
The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html.
@@ -802,7 +802,7 @@ first. There is also a developer's wiki at
Allow tables to bypass WAL writes and just fsync() dirty pages on commit. This should be implemented using ALTER TABLE, e.g. ALTER - TABLE PERSISTENCE [ DROP | TRUNCATE | DEFAULT ]. Tables using + TABLE PERSISTENCE [ DROP | TRUNCATE | DEFAULT ]. Tables using non-default logging should not use referential integrity with default-logging tables. A table without dirty buffers during a crash could perhaps avoid the drop/truncate.