Re: WHERE IN (subselect) versus WHERE IN (1,2,3,)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Kevin Goess <kgoess(at)bepress(dot)com>
Cc: Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>, pgsql-general(at)postgresql(dot)org
Subject: Re: WHERE IN (subselect) versus WHERE IN (1,2,3,)
Date: 2012-03-20 03:27:08
Message-ID: 15818.1332214028@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

I wrote:
> You've still got a nasty join-size estimation error:

>> -> Nested Loop (cost=6.18..1939.43 rows=411736 width=8) (actual
>> time=0.203..3.487 rows=35 loops=1)

> It's not apparent why that's so far off ...

What PG version is this, anyway? It strikes me that this estimation
error might have something with the eqjoinsel bugs that we repaired
in 9.0.5. I'm not having any luck reproducing such a bogus estimate
with current code, either, though that may just mean you've omitted
some critical info about how the tables are set up.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Kevin Goess 2012-03-20 07:23:35 Re: WHERE IN (subselect) versus WHERE IN (1,2,3,)
Previous Message Kiriakos Georgiou 2012-03-20 00:48:44 Re: Anonymized database dumps