Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id 69E1CB6127F for ; Wed, 1 Jun 2011 17:47:52 -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 85256-03 for ; Wed, 1 Jun 2011 20:47:41 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by mail.postgresql.org (Postfix) with ESMTP id 35CA4B61261 for ; Wed, 1 Jun 2011 17:47:41 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id p51Klahx024708; Wed, 1 Jun 2011 16:47:36 -0400 (EDT) To: Robert Haas cc: =?ISO-8859-1?Q?C=E9dric_Villemain?= , panam , PostgreSQL-development Subject: Re: [PERFORM] Hash Anti Join performance degradation In-reply-to: References: <1306210464806-4420974.post@n5.nabble.com> <4DDB47BC.8030504@postnewspapers.com.au> <1306247697267-4422247.post@n5.nabble.com> <4DDC6109.7060708@postnewspapers.com.au> <1306341749094-4425890.post@n5.nabble.com> <4DDDBD96.4010809@postnewspapers.com.au> <1306413217406-4428435.post@n5.nabble.com> <7913.1306900062@sss.pgh.pa.us> <24247.1306959956@sss.pgh.pa.us> <24461.1306960516@sss.pgh.pa.us> Comments: In-reply-to Robert Haas message dated "Wed, 01 Jun 2011 16:43:29 -0400" Date: Wed, 01 Jun 2011 16:47:36 -0400 Message-ID: <24707.1306961256@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.91 tagged_above=-5 required=5 tests=BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201106/57 X-Sequence-Number: 188770 Robert Haas writes: > I guess the real issue here is that m1.id < m2.id has to be evaluated > as a filter condition rather than a join qual. Well, if you can invent an optimized join technique that works for inequalities, go for it ... but I think you should get at least a PhD thesis out of that. regards, tom lane