From c441e26ee8022862b3c3906609e5a386696d2d3b Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Wed, 1 Aug 2007 23:13:31 +0000 Subject: Done: < * Allow buffered WAL writes and fsync --- doc/src/FAQ/TODO.html | 11 ++--------- 1 file changed, 2 insertions(+), 9 deletions(-) (limited to 'doc/src/FAQ') diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html index d8805855a1..4c3615b6c9 100644 --- a/doc/src/FAQ/TODO.html +++ b/doc/src/FAQ/TODO.html @@ -8,7 +8,7 @@

PostgreSQL TODO List

Current maintainer: Bruce Momjian (bruce@momjian.us)
-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 -- cgit v1.2.3