| From: | Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Dimitri Fontaine <dim(at)hi-media(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: *_collapse_limit, geqo_threshold |
| Date: | 2009-07-10 18:44:49 |
| Message-ID: | 3073cc9b0907101144g5d850773lba16b787c7381ebf@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jul 10, 2009 at 10:22 AM, Robert Haas<robertmhaas(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-07-10 18:48:45 | Re: *_collapse_limit, geqo_threshold |
| Previous Message | Robert Haas | 2009-07-10 18:32:58 | Re: *_collapse_limit, geqo_threshold |