From: Peter Eisentraut <peter_e@gmx.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Subject: Re: Nested loops overpriced
Date: Wed, 9 May 2007 13:58:25 +0200
User-Agent: KMail/1.9.5
Cc: pgsql-performance@postgresql.org
References: <200705081722.16731.peter_e@gmx.net>
	<1987.1178639593@sss.pgh.pa.us>
In-Reply-To: <1987.1178639593@sss.pgh.pa.us>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200705091358.25748.peter_e@gmx.net>

Am Dienstag, 8. Mai 2007 17:53 schrieb Tom Lane:
> Hmm, I'd have expected it to discount the repeated indexscans a lot more
> than it seems to be doing for you.  As an example in the regression
> database, note what happens to the inner indexscan cost estimate when
> the number of outer tuples grows:

I can reproduce your results in the regression test database. 8.2.1 and 8.2.4 
behave the same.

I checked the code around cost_index(), and the assumptions appear to be 
correct (at least this query doesn't produce wildly unusual data).  
Apparently, however, the caching effects are much more significant than the 
model takes into account.

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