Re: merge>hash>loop

From: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Markus Schaber <schabi(at)logix-tt(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: merge>hash>loop
Date: 2006-04-18 23:15:52
Message-ID: 20060418231552.GN49405@pervasive.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Tue, Apr 18, 2006 at 06:22:26PM -0400, Tom Lane wrote:
> "Jim C. Nasby" <jnasby(at)pervasive(dot)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...
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Jim C. Nasby 2006-04-18 23:22:26 Re: merge>hash>loop
Previous Message Jim C. Nasby 2006-04-18 23:13:53 Re: Multicolumn order by