Re: enable_joinremoval - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: enable_joinremoval
Date
Msg-id 20100329144219.GA3925@alvh.no-ip.org
Whole thread Raw
In response to Re: enable_joinremoval  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: enable_joinremoval
Re: enable_joinremoval
List pgsql-hackers
Tom Lane escribió:
> Robert Haas <robertmhaas@gmail.com> writes:
> > On Mon, Mar 29, 2010 at 4:33 AM, Simon Riggs <simon@2ndquadrant.com> wrote:
> >> So I think we need a parameter for join removal also.
> 
> > I had this in my original patch but Tom wanted it taken out.
> 
> And I still don't want it.  We are NOT going in the direction of adding
> an enable_ knob for every single planner activity --- do you have the
> faintest idea how many there would be?  We have such knobs for a small
> number of cases where it's arguable that the action might be the wrong
> thing for a particular query.  Join removal, if applicable, can't
> possibly be the wrong choice; it's better than every other join strategy.

It seems that what's really needed is some debug output to be able to
find out what it did.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: enable_joinremoval
Next
From: Tom Lane
Date:
Subject: Re: Using HStore type in TSearch