1
0
mirror of https://github.com/postgres/postgres.git synced 2025-07-02 09:02:37 +03:00

Add description:

>
>   O_DIRECT doesn't have the same media write guarantees as fsync, so it
>   is in addition to the fsync method, not in place of it.
>
This commit is contained in:
Bruce Momjian
2005-06-04 16:53:48 +00:00
parent 1bc9235224
commit 487990e1f1
2 changed files with 9 additions and 2 deletions

View File

@ -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:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</a>)<br/>
Last updated: Fri Jun 3 17:42:10 EDT 2005
Last updated: Sat Jun 4 12:53:41 EDT 2005
</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>.
@ -663,6 +663,9 @@ first.
</p>
</li><li>Consider use of open/fcntl(O_DIRECT) to minimize OS caching,
especially for WAL writes
<p> O_DIRECT doesn't have the same media write guarantees as fsync, so it
is in addition to the fsync method, not in place of it.
</p>
</li><li>-<em>Cache last known per-tuple offsets to speed long tuple access</em>
</li><li>Speed up COUNT(*)
<p> We could use a fixed row count and a +/- count to follow MVCC