Re: O_DIRECT in freebsd - Mailing list pgsql-hackers

From Gavin Sherry
Subject Re: O_DIRECT in freebsd
Date
Msg-id Pine.LNX.4.21.0306180957240.31214-100000@linuxworld.com.au
Whole thread Raw
In response to Re: O_DIRECT in freebsd  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: O_DIRECT in freebsd  ("Jim C. Nasby" <jim@nasby.net>)
Re: O_DIRECT in freebsd  ("Jim C. Nasby" <jim@nasby.net>)
List pgsql-hackers
On Tue, 17 Jun 2003, Tom Lane wrote:

> "Christopher Kings-Lynne" <chriskl@familyhealth.com.au> writes:
> > The reason I mention it is that Postgres already supports O_DIRECT I think
> > on some other platforms (for whatever reason).
> 
> [ sounds of grepping... ]  No.  The only occurrence of O_DIRECT in the
> source tree is in TODO:
> 
> * Consider use of open/fcntl(O_DIRECT) to minimize OS caching
> 
> I personally disagree with this TODO item for the same reason Sean
> cited: Postgres is designed and tuned to rely on OS-level disk caching,
> and bypassing that cache is far more likely to hurt our performance than
> help it.

DB2 and Oracle, from memory, allow users to pass hints to the planner to
use/not use file system caching. This could be useful if you had an
application retrieving a large amount of data on an adhoc basis. The large
retrieval would empty out the disk cache there by negatively impacting
upon other applications operating on data which should be cached.

Gavin



pgsql-hackers by date:

Previous
From: Andreas Pflug
Date:
Subject: Re: Extending PostgreSQL in C or C++
Next
From: deststar
Date:
Subject: Re: sa_family_t in cygwin compile of cvs