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

From Dimitri Fontaine
Subject Re: *_collapse_limit, geqo_threshold
Date
Msg-id D98046E0-6DF0-4074-9AF6-694523CE6770@hi-media.com
Whole thread Raw
In response to Re: *_collapse_limit, geqo_threshold  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: *_collapse_limit, geqo_threshold  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
List pgsql-hackers
Le 7 juil. 09 à 21:16, Robert Haas a écrit :
> Now, here's another thought: if we think it's reasonable for people
> to want to explicitly specify the join order, a GUC isn't really the
> best fit, because it's all or nothing.  Maybe we'd be better off
> dropping the GUCs entirely and adding some other bit of syntax that
> forces the join order, but only for that particular join.

MySQL calls them Straight Joins: http://www.mysqlperformanceblog.com/2006/12/28/mysql-session-variables-and-hints/

I'm not sure our best move here would be in this direction :)
--
dim

pgsql-hackers by date:

Previous
From: Dimitri Fontaine
Date:
Subject: Re: *_collapse_limit, geqo_threshold
Next
From: Tom Lane
Date:
Subject: Re: Have \d show child tables that inherit from the specified parent