| From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Improving planning of outer joins |
| Date: | 2005-12-16 02:19:10 |
| Message-ID: | 43A2241E.7070005@familyhealth.com.au |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> I'm not sure whether we'd need any additional planner knobs to control
> this. I think that the existing join_collapse_limit GUC variable should
> continue to exist, but its effect on left/right joins will be the same as
> for inner joins. If anyone wants to force join order for outer joins more
> than for inner joins, we'd need some other control setting, but I don't
> currently see why that would be very useful.
>
> Does this seem like a reasonable agenda, or am I thinking too small?
I think it's fantastic - it's a big complaint about planning we see
often in the IRC channel.
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2005-12-16 02:19:20 | Re: Improving planning of outer joins |
| Previous Message | Dann Corbit | 2005-12-16 02:02:55 | Re: Which qsort is used |