From: Mark Kirkwood <markir@paradise.net.nz>
To: Jim C. Nasby <jnasby@pervasive.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Markus Schaber <schabi@logix-tt.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: merge>hash>loop
Date: Wed, 19 Apr 2006 16:47:40 +1200
Message-ID: <4445C0EC.2060407@paradise.net.nz> (raw)
In-Reply-To: <20060418231552.GN49405@pervasive.com>
References: <1145029009.3422.31.camel@spectre.intellivid.com>
<10000.1145031205@sss.pgh.pa.us>
<1145033149.3422.41.camel@spectre.intellivid.com>
<11035.1145033929@sss.pgh.pa.us>
<4444C4CF.2000106@logix-tt.com>
<20060418215238.GK49405@pervasive.com>
<19388.1145398946@sss.pgh.pa.us>
<20060418231552.GN49405@pervasive.com>
Jim C. Nasby wrote:
> On Tue, Apr 18, 2006 at 06:22:26PM -0400, Tom Lane wrote:
>> "Jim C. Nasby" <jnasby@pervasive.com> writes:
>>> Actually, if you run with stats_block_level turned on you have a
>>> first-order approximation of what is and isn't cached.
>> Only if those stats decayed (pretty fast) with time; which they don't.
>
> Good point. :/ I'm guessing there's no easy way to see how many blocks
> for a given relation are in shared memory, either...
contrib/pg_buffercache will tell you this - what buffers from what
relation are in shared_buffers (if you want to interrogate the os file
buffer cache, that's a different story - tho I've been toying with doing
a utility for Freebsd that would do this).
Cheers
Mark
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: markir@paradise.net.nz, jnasby@pervasive.com, tgl@sss.pgh.pa.us, schabi@logix-tt.com
Subject: Re: merge>hash>loop
In-Reply-To: <4445C0EC.2060407@paradise.net.nz>
* 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