From: Peter Eisentraut <peter_e@gmx.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Subject: Re: Nested loops overpriced
Date: Thu, 10 May 2007 17:35:06 +0200
User-Agent: KMail/1.9.5
Cc: pgsql-performance@postgresql.org
References: <200705081722.16731.peter_e@gmx.net>
	<200705091817.45056.peter_e@gmx.net>
	<28620.1178732406@sss.pgh.pa.us>
In-Reply-To: <28620.1178732406@sss.pgh.pa.us>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
Content-Disposition: inline
Message-Id: <200705101735.06509.peter_e@gmx.net>

Am Mittwoch, 9. Mai 2007 19:40 schrieb Tom Lane:
> Hmmm ... I see at least part of the problem, which is that email_header
> is joined twice in this query, which means that it's counted twice in
> figuring the total volume of pages competing for cache space.  So the
> thing thinks cache space is oversubscribed nearly 3X when in reality
> the database is fully cached.

I should add that other, similar queries in this database that do not involve 
joining the same table twice produce seemingly optimal plans.  (It picks hash 
joins which are actually faster than nested loops.)

-- 
Peter Eisentraut
http://developer.postgresql.org/~petere/