| From: | Dimitri Fontaine <dfontaine(at)hi-media(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: *_collapse_limit, geqo_threshold |
| Date: | 2009-07-07 19:33:54 |
| Message-ID: | D98046E0-6DF0-4074-9AF6-694523CE6770@hi-media.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-07-07 19:35:52 | Re: Have \d show child tables that inherit from the specified parent |
| Previous Message | Jeff Davis | 2009-07-07 19:30:52 | Re: WIP: generalized index constraints |