mirror/postgresql
2
0
Fork 0
mirror of https://git.postgresql.org/git/postgresql.git synced 2025-01-24 18:55:04 +08:00
Code Issues Packages Projects Releases Wiki Activity

Done:

Browse Source 
< * Allow buffered WAL writes and fsync
This commit is contained in:
Bruce Momjian 2007-08-01 23:13:31 +00:00
parent 4a78cdeb6b
commit c441e26ee8
2 changed files with 4 additions and 19 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
doc/TODO
View File

@ -1,7 +1,7 @@
PostgreSQL TODO List PostgreSQL TODO List
==================== ====================
Current maintainer: Bruce Momjian (bruce@momjian.us) 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 The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html. 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 rotation to fsync again. One idea is to write the WAL to different
offsets that might reduce the rotational delay. offsets that might reduce the rotational delay.
* Allow buffered WAL writes and fsync * -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 WAL logging to be turned off for a table, but the table * Allow WAL logging to be turned off for a table, but the table
might be dropped or truncated during crash recovery [walcontrol] might be dropped or truncated during crash recovery [walcontrol]

11
doc/src/FAQ/TODO.html
View File

@ -8,7 +8,7 @@
<body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF"> <body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF">
<h1><a name="section_1">PostgreSQL TODO List</a></h1> <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/> <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>
<p>The most recent version of this document can be viewed at<br/> <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>. <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 rotation to fsync again. One idea is to write the WAL to different
offsets that might reduce the rotational delay. offsets that might reduce the rotational delay.
</p> </p>
</li><li>Allow buffered WAL writes and fsync </li><li>-<em>Allow buffered WAL writes and fsync</em>
<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>Allow WAL logging to be turned off for a table, but the table </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>] 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 <p> Allow tables to bypass WAL writes and just fsync() dirty pages on