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:
parent
1bc9235224
commit
487990e1f1
6
doc/TODO
6
doc/TODO
@ -2,7 +2,7 @@
|
|||||||
PostgreSQL TODO List
|
PostgreSQL TODO List
|
||||||
====================
|
====================
|
||||||
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
|
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
|
||||||
Last updated: Fri Jun 3 17:42:10 EDT 2005
|
Last updated: Sat Jun 4 12:53:41 EDT 2005
|
||||||
|
|
||||||
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.
|
||||||
@ -722,6 +722,10 @@ Cache
|
|||||||
|
|
||||||
* Consider use of open/fcntl(O_DIRECT) to minimize OS caching,
|
* Consider use of open/fcntl(O_DIRECT) to minimize OS caching,
|
||||||
especially for WAL writes
|
especially for WAL writes
|
||||||
|
|
||||||
|
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.
|
||||||
|
|
||||||
* -Cache last known per-tuple offsets to speed long tuple access
|
* -Cache last known per-tuple offsets to speed long tuple access
|
||||||
* Speed up COUNT(*)
|
* Speed up COUNT(*)
|
||||||
|
|
||||||
|
@ -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:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</a>)<br/>
|
<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>
|
||||||
<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>.
|
||||||
@ -663,6 +663,9 @@ first.
|
|||||||
</p>
|
</p>
|
||||||
</li><li>Consider use of open/fcntl(O_DIRECT) to minimize OS caching,
|
</li><li>Consider use of open/fcntl(O_DIRECT) to minimize OS caching,
|
||||||
especially for WAL writes
|
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>-<em>Cache last known per-tuple offsets to speed long tuple access</em>
|
||||||
</li><li>Speed up COUNT(*)
|
</li><li>Speed up COUNT(*)
|
||||||
<p> We could use a fixed row count and a +/- count to follow MVCC
|
<p> We could use a fixed row count and a +/- count to follow MVCC
|
||||||
|
Loading…
x
Reference in New Issue
Block a user