From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Moshe Jacobson <moshe(at)neadwerx(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org, Robert Mowlavi <robert(at)neadwerx(dot)com>, Chris Autry <chris(at)neadwerx(dot)com> |
Subject: | Re: LEFT JOINs not optimized away when not needed |
Date: | 2014-07-08 20:40:28 |
Message-ID: | 709.1404852028@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
Moshe Jacobson <moshe(at)neadwerx(dot)com> writes:
> On Tue, Jul 8, 2014 at 3:47 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> AFAICS, the eight
>> un-removed joins are either joining to non-unique keys, or can't be
>> removed because their tables are needed to provide joining columns for
>> un-removable joins.
> My point is that even if the column to which we are joining is a non-unique
> key, there should be no need to look at that table if the output does not
> include any values from that table, and there are no filters on that
> table's values, and all output columns are in the GROUP BY. Is the planner
> not smart enough to notice this?
No. There is nothing about GROUP BY in the join removal logic.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Moshe Jacobson | 2014-07-08 20:44:39 | Re: LEFT JOINs not optimized away when not needed |
Previous Message | Moshe Jacobson | 2014-07-08 19:57:21 | Re: LEFT JOINs not optimized away when not needed |
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2014-07-08 20:42:40 | Re: Doing better at HINTing an appropriate column within errorMissingColumn() |
Previous Message | Bruce Momjian | 2014-07-08 20:21:14 | Re: Securing "make check" (CVE-2014-0067) |