Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id C4521633226 for ; Mon, 29 Mar 2010 13:29:33 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 80209-01 for ; Mon, 29 Mar 2010 16:29:23 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-fx0-f225.google.com (mail-fx0-f225.google.com [209.85.220.225]) by mail.postgresql.org (Postfix) with ESMTP id CC65463350B for ; Mon, 29 Mar 2010 13:29:12 -0300 (ADT) Received: by fxm25 with SMTP id 25so2430fxm.3 for ; Mon, 29 Mar 2010 09:29:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=UhbekT5GdjwFpufz3771Mar25Sw/NJksJ9nyJmlMrEI=; b=O1gueULMrmsEi2e5zrLqGu+Nnrt0NgDMscnhMfPTKBXdSdwMlNZnvWDoF3nfEU3Yrj d4WAaLb5Bicw36chPNGAMzdTzAVHu3n4J8Gw1N+Bz/ABaofcic3sorVkwSJaf3uPWERC iLgD/sX34XpoYUcHvCk2b5MlsbgrzQHcznN+Q= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=TExaLrI/Ivehx84Z9ctkK8snC9OzqQRGJWMsoAXu2osLfGn+q4KUpZuMnFih/czGfy Vm4J3WTATHIek4rIMwMYeVsxSP2VRpS5kuVtRVH98CXTgsWY7aecCAzVkkn/R0gPdwk4 D6e60Mj+pbd8ewuD3sK3DsH9hfQRp2a9DKYpA= MIME-Version: 1.0 Received: by 10.239.161.83 with HTTP; Mon, 29 Mar 2010 09:29:11 -0700 (PDT) In-Reply-To: <14825.1269879474@sss.pgh.pa.us> References: <1269851630.3684.3636.camel@ebony> <603c8f071003290637q14d431f7j90afabd6fd2ec952@mail.gmail.com> <12679.1269873374@sss.pgh.pa.us> <603c8f071003290820h3553d223le3b5228f789608f9@mail.gmail.com> <4BB0CF3D.8090701@2ndquadrant.com> <603c8f071003290910l310c0e18v6b8986a22c6c4836@mail.gmail.com> <14825.1269879474@sss.pgh.pa.us> Date: Mon, 29 Mar 2010 12:29:11 -0400 Received: by 10.239.188.129 with SMTP id p1mr497990hbh.190.1269880151394; Mon, 29 Mar 2010 09:29:11 -0700 (PDT) Message-ID: <603c8f071003290929x3d36be21t848d2f7244c0cf5b@mail.gmail.com> Subject: Re: enable_joinremoval From: Robert Haas To: Tom Lane Cc: Greg Smith , Simon Riggs , pgsql-hackers@postgresql.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.599 tagged_above=-10 required=5 tests=BAYES_00=-2.599 X-Spam-Level: X-Archive-Number: 201003/1159 X-Sequence-Number: 159935 On Mon, Mar 29, 2010 at 12:17 PM, Tom Lane wrote: > Robert Haas writes: >> On Mon, Mar 29, 2010 at 12:03 PM, Greg Smith wrot= e: >>> at the top of my list in this area for 9.1 is to track down the rumored >>> patch that exports information about the rejected plans considered and = get >>> that comitted. =A0That always seems what I want to look at for answerin= g the >>> question "why this plan instead of what I was expecting?" > >> Having looked at that patch, I am skeptical of it, but we can >> certainly take a fresh look. > > The problem with this line of thought is that it imagines you can look > at worked-out alternative plans. =A0You can't, because the planner doesn'= t > pursue rejected alternatives that far (and you'd not want to wait long > enough for it to do so...) Right. And that's not what the patch did. But a detailed discussion of this topic should be (a) conducted on a separate thread and (b) occur after we've all refamiliarized ourselves with it. ...Robert