Re: Caching by Postgres - Mailing list pgsql-performance

From Tom Lane
Subject Re: Caching by Postgres
Date
Msg-id 21392.1124860042@sss.pgh.pa.us
Whole thread Raw
In response to Re: Caching by Postgres  (Gavin Sherry <swm@alcove.com.au>)
Responses Re: Caching by Postgres  (Gavin Sherry <swm@alcove.com.au>)
List pgsql-performance
Gavin Sherry <swm@alcove.com.au> writes:
> A filesystem could, in theory, help us by providing an API which allows us
> to tell the file system either: the way we'd like it to read ahead, the
> fact that we don't want it to read ahead or the way we'd like it to cache
> (or not cache) data. The thing is, most OSes provide interfaces to do this
> already and we make only little use of them (I'm think of
> madv_sequential(), madv_random(), POSIX fadvise(), the various flags to
> open() which AIX, HPUX, Solaris provide).

Yeah ... the main reason we've not spent too much time on that sort of
stuff is that *it's not portable*.  And with all due respect to Hans,
special tweaks for one filesystem are even less interesting than special
tweaks for one OS.

            regards, tom lane

pgsql-performance by date:

Previous
From: "Jeffrey W. Baker"
Date:
Subject: Re: Read/Write block sizes
Next
From: Tom Lane
Date:
Subject: Re: Read/Write block sizes