From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Gavin Sherry <swm(at)alcove(dot)com(dot)au> |
Cc: | PFC <lists(at)boutiquenumerique(dot)com>, William Yu <wyu(at)talisys(dot)com>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Caching by Postgres |
Date: | 2005-08-24 05:07:22 |
Message-ID: | 21392.1124860042@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Gavin Sherry <swm(at)alcove(dot)com(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-08-24 05:10:20 | Re: Read/Write block sizes |
Previous Message | Gavin Sherry | 2005-08-24 04:38:02 | Re: Caching by Postgres |