From: Gavin Sherry <swm@alcove.com.au>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: PFC <lists@boutiquenumerique.com>
Cc: William Yu <wyu@talisys.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Caching by Postgres
Date: Wed, 24 Aug 2005 15:24:07 +1000 (EST)
Message-ID: <Pine.LNX.4.58.0508241510060.5493@linuxworld.com.au> (raw)
In-Reply-To: <21392.1124860042@sss.pgh.pa.us>
References: <20050823171045.12112.qmail@web51309.mail.yahoo.com>
<20050823124323.710a9dd3.frank@wiles.org>
<430B6DE3.6040109@sun.com>
<deg68k$16gh$1@news.hub.org>
<op.svzh7sqdth1vuj@localhost>
<Pine.LNX.4.58.0508241425080.5141@linuxworld.com.au>
<21392.1124860042@sss.pgh.pa.us>
On Wed, 24 Aug 2005, Tom Lane wrote:
> 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.
Right.
As an aside, it seems to me that if there is merit in all this low level
interaction with the file system (not to mention the other platform
specific microoptimisations which come up regularly on the lists) then the
companies currently producing niche commercial releases of PostgreSQL
should be taking advantage of them: if it increases performance, then
there's a reason to buy as opposed to just downloading the OSS version.
Gavin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: swm@alcove.com.au, tgl@sss.pgh.pa.us, lists@boutiquenumerique.com, wyu@talisys.com
Subject: Re: Caching by Postgres
In-Reply-To: <Pine.LNX.4.58.0508241510060.5493@linuxworld.com.au>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox