diff options
| -rw-r--r-- | doc/TODO | 12 | ||||
| -rw-r--r-- | doc/src/FAQ/TODO.html | 11 |
2 files changed, 4 insertions, 19 deletions
@@ -1,7 +1,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. @@ -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 d8805855a1e..4c3615b6c9b 100644 --- a/doc/src/FAQ/TODO.html +++ b/doc/src/FAQ/TODO.html @@ -8,7 +8,7 @@ <body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF"> <h1><a name="section_1">PostgreSQL TODO List</a></h1> <p>Current maintainer: Bruce Momjian (<a href="mailto:bruce@momjian.us">bruce@momjian.us</a>)<br/> -Last updated: Tue Jul 17 20:15:52 EDT 2007 +Last updated: Wed Aug 1 19:13:20 EDT 2007 </p> <p>The most recent version of this document can be viewed at<br/> <a href="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>. @@ -1182,14 +1182,7 @@ first. There is also a developer's wiki at<br/> rotation to fsync again. One idea is to write the WAL to different offsets that might reduce the rotational delay. </p> - </li><li>Allow buffered WAL writes and fsync -<p> 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. -</p> + </li><li>-<em>Allow buffered WAL writes and fsync</em> </li><li>Allow WAL logging to be turned off for a table, but the table might be dropped or truncated during crash recovery [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?walcontrol">walcontrol</a>] <p> Allow tables to bypass WAL writes and just fsync() dirty pages on |