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

From Tom Lane
Subject Re: *_collapse_limit, geqo_threshold
Date
Msg-id 27107.1247251725@sss.pgh.pa.us
Whole thread Raw
In response to Re: *_collapse_limit, geqo_threshold  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Responses Re: *_collapse_limit, geqo_threshold  (Ron Mayer <rm_pg@cheapcomplexdevices.com>)
Re: *_collapse_limit, geqo_threshold  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
"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.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Jaime Casanova
Date:
Subject: Re: *_collapse_limit, geqo_threshold
Next
From: Josh Berkus
Date:
Subject: Re: [pgsql-www] commitfest.postgresql.org