Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id 9F0801337C93 for ; Mon, 2 May 2011 13:31:43 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 17818-01-5 for ; Mon, 2 May 2011 16:31:36 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mail.yagni.com (mail.yagni.com [65.114.230.116]) by mail.postgresql.org (Postfix) with ESMTP id 67E941337B3E for ; Mon, 2 May 2011 13:16:30 -0300 (ADT) Received: from phoenix.databill.com ([65.114.230.114] helo=[10.0.0.15]) by mail.yagni.com with esmtpsa (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1QGvm2-0005pw-Uj; Mon, 02 May 2011 09:15:02 -0700 Message-ID: <4DBED871.4010306@yagni.com> Date: Mon, 02 May 2011 09:14:41 -0700 From: Wayne Conrad User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.16) Gecko/20110303 Icedove/3.0.11 MIME-Version: 1.0 To: Tom Lane CC: pgsql-performance@postgresql.org Subject: Re: 8.4.7, incorrect estimate References: <4DBB024B.5050500@databill.com> <4DBAC75C020000250003D06B@gw.wicourts.gov> <4DBEAF7B.1060409@yagni.com> <21729.1304349118@sss.pgh.pa.us> In-Reply-To: <21729.1304349118@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-0.242 tagged_above=-10 required=5 tests=BAYES_00=-1.9, DNS_FROM_RFC_BOGUSMX=1.668, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201105/19 X-Sequence-Number: 43528 On 05/02/11 08:11, Tom Lane wrote: > Wayne Conrad writes: >> On 04/29/11 12:12, Kevin Grittner wrote: >>> Out of curiosity, what do you get with?: >>> >>> explain analyze >>> select >>> page_number, >>> ps_id, >>> ps_page_id >>> from ps_page p >>> where exists >>> ( >>> select * from documents_ps_page d >>> where d.ps_page_id = p.ps_page_id >>> and exists >>> (select * from temp_document_ids t >>> where t.document_id = d.document_id) >>> ) >>> order by ps_page_id > >> Merge Semi Join (cost=186501.69..107938082.91 rows=29952777 width=12) >> (actual time=242801.828..244572.318 rows=5 loops=1) >> Merge Cond: (p.ps_page_id = d.ps_page_id) >> -> Index Scan using ps_page_pkey on ps_page p >> (cost=0.00..2995637.47 rows=86141904 width=12) (actual >> time=0.052..64140.510 rows=85401688 loops=1) >> -> Index Scan using documents_ps_page_ps_page_id_idx on >> documents_ps_page d (cost=0.00..104384546.06 rows=37358320 width=4) >> (actual time=161483.657..163254.131 rows=5 loops=1) >> Filter: (alternatives: SubPlan 1 or hashed SubPlan 2) >> SubPlan 1 >> -> Seq Scan on temp_doc_ids t (cost=0.00..1.35 rows=1 >> width=0) (never executed) >> Filter: (document_id = $0) >> SubPlan 2 >> -> Seq Scan on temp_doc_ids t (cost=0.00..1.34 rows=5 >> width=35) (actual time=0.005..0.007 rows=5 loops=1) >> Total runtime: 244572.432 ms >> (11 rows) > > [ pokes at that ... ] I think what you've got here is an oversight in > the convert-EXISTS-to-semijoin logic: it pulls up the outer EXISTS but > fails to recurse on it, which would be needed to convert the lower > EXISTS into a semijoin as well, which is what's needed in order to get > a non-bogus selectivity estimate for it. > > I'll take a look at fixing that, but not sure if it'll be reasonable to > back-patch or not. In the meantime, you need to look into restructuring > the query to avoid nesting the EXISTS probes, if possible. > > regards, tom lane > Tom, Thanks for looking at this. FYI, the same problem occurs when nesting "where ... in (...)" (see start of thread, or I can repost it if you want). In any case, I can make the problem go away by using another layer of temporary table to avoid the nesting. That's what I'll do for now. I'm not worried about back-patches to fix this in 8.4. We'll be upgrading this box to 9 at some point; we'll just pick up any fix when it hits 9. Best Regards, Wayne Conrad