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

From Robert Haas
Subject Re: *_collapse_limit, geqo_threshold
Date
Msg-id 603c8f070907102121j730ef196s103b5efbb28a49ea@mail.gmail.com
Whole thread Raw
In response to Re: *_collapse_limit, geqo_threshold  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Fri, Jul 10, 2009 at 2:48 PM, Tom Lane<tgl@sss.pgh.pa.us> wrote:
> "Kevin Grittner" <Kevin.Grittner@wicourts.gov> writes:
>> You do, but it's been pretty rare in my experience, and we're
>> considering alternatives which give a lot less flexibility that this.
>
> I dunno about "considering".  We've already wasted vastly more time on
> this than it's worth.  AFAIR there has never been one single user
> request for the ability to partially constrain join order.  I think we
> should do an enable_join_ordering boolean and quit wasting brainpower on
> the issue.

Patch attached.

...Robert

Attachment

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: *_collapse_limit, geqo_threshold
Next
From: Theo Schlossnagle
Date:
Subject: Re: concurrent index builds unneeded lock?