|
8 | 8 | <bodybgcolor="#FFFFFF"text="#000000"link="#FF0000"vlink="#A00000"alink="#0000FF"> |
9 | 9 | <h1><aname="section_1">PostgreSQL TODO List</a></h1> |
10 | 10 | <p>Current maintainer: Bruce Momjian (<ahref="mailto:bruce@momjian.us">bruce@momjian.us</a>)<br/> |
11 | | -Last updated:Tue Jul 17 20:15:52 EDT 2007 |
| 11 | +Last updated:Wed Aug 1 19:13:20 EDT 2007 |
12 | 12 | </p> |
13 | 13 | <p>The most recent version of this document can be viewed at<br/> |
14 | 14 | <ahref="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>. |
@@ -1182,14 +1182,7 @@ <h1><a name="section_18">Write-Ahead Log</a></h1> |
1182 | 1182 | rotation to fsync again. One idea is to write the WAL to different |
1183 | 1183 | offsets that might reduce the rotational delay. |
1184 | 1184 | </p> |
1185 | | -</li><li>Allow buffered WAL writes and fsync |
1186 | | -<p> Instead of guaranteeing recovery of all committed transactions, this |
1187 | | - would provide improved performance by delaying WAL writes and fsync |
1188 | | - so an abrupt operating system restart might lose a few seconds of |
1189 | | - committed transactions but still be consistent. We could perhaps |
1190 | | - remove the 'fsync' parameter (which results in an an inconsistent |
1191 | | - database) in favor of this capability. |
1192 | | -</p> |
| 1185 | +</li><li>-<em>Allow buffered WAL writes and fsync</em> |
1193 | 1186 | </li><li>Allow WAL logging to be turned off for a table, but the table |
1194 | 1187 | might be dropped or truncated during crash recovery [<ahref="http://momjian.postgresql.org/cgi-bin/pgtodo?walcontrol">walcontrol</a>] |
1195 | 1188 | <p> Allow tables to bypass WAL writes and just fsync() dirty pages on |
|