From 487990e1f17e7898f595e4ab7589c51e7d61da1b Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Sat, 4 Jun 2005 16:53:48 +0000 Subject: 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. > --- doc/src/FAQ/TODO.html | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) (limited to 'doc/src') diff --git a/doc/src/FAQ/TODO.html b/doc/src/FAQ/TODO.html index 16df40b9ef9..e42a8f921af 100644 --- a/doc/src/FAQ/TODO.html +++ b/doc/src/FAQ/TODO.html @@ -8,7 +8,7 @@

PostgreSQL TODO List

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
http://www.postgresql.org/docs/faqs.TODO.html. @@ -663,6 +663,9 @@ first.

Consider use of open/fcntl(O_DIRECT) to minimize OS caching, 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

Speed up COUNT(*)

We could use a fixed row count and a +/- count to follow MVCC -- cgit v1.2.3