Re: *_collapse_limit, geqo_threshold - Mailing list pgsql-hackers

From Robert Haas
Subject Re: *_collapse_limit, geqo_threshold
Date
Msg-id A0E15881-6B55-4B09-B2CB-98A8B651141A@gmail.com
Whole thread Raw
In response to Re: *_collapse_limit, geqo_threshold  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Responses Re: *_collapse_limit, geqo_threshold
Re: *_collapse_limit, geqo_threshold
List pgsql-hackers
On Jul 7, 2009, at 3:03 PM, "Kevin Grittner" <Kevin.Grittner@wicourts.gov > wrote:

> Robert Haas <robertmhaas@gmail.com> wrote:
>
>> if we think it's reasonable for people to want to explicitly specify
>> the join order
>
> Regardless of the syntax (GUC or otherwise), that is an optimizer
> hint.  I thought we were trying to avoid those.

I guess my point is that there's not a lot of obvious benefit in  
allowing the functionality to exist but handicapping it so that it's  
useful in as few cases as possible.  If the consensus is that we want  
half a feature (but not more or less than half), that's OK with me,  
but it's not obvious to me why we should choose to want that.

...Robert


pgsql-hackers by date:

Previous
From: Jeff Davis
Date:
Subject: Re: WIP: generalized index constraints
Next
From: Tom Lane
Date:
Subject: Re: *_collapse_limit, geqo_threshold