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

From Jaime Casanova
Subject Re: *_collapse_limit, geqo_threshold
Date
Msg-id 3073cc9b0907101144g5d850773lba16b787c7381ebf@mail.gmail.com
Whole thread Raw
In response to Re: *_collapse_limit, geqo_threshold  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: *_collapse_limit, geqo_threshold  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Fri, Jul 10, 2009 at 10:22 AM, Robert Haas<robertmhaas@gmail.com> wrote:
> I took a look at this and it seems that #3 can be implemented with
> essentially no additional code (the handful of lines I added where
> more than balanced out by some simplifications in ruleutils.c).  Of
> course you still don't have to like it.  :-)
>
> Patch attached.
>

! SELECT * FROM a INNER FORCE JOIN (b INNER FORCE JOIN c ON (b.ref =
c.id)) ON (a.id = b.id);

what's next? FORCE INDEX?
once we implement one hint like this the complaints about the others
will lose force


--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: *_collapse_limit, geqo_threshold
Next
From: Tom Lane
Date:
Subject: Re: *_collapse_limit, geqo_threshold