Re: LEFT JOINs not optimized away when not needed - Mailing list pgsql-bugs

From Tom Lane
Subject Re: LEFT JOINs not optimized away when not needed
Date
Msg-id 16398.1404924845@sss.pgh.pa.us
Whole thread Raw
In response to Re: LEFT JOINs not optimized away when not needed  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: LEFT JOINs not optimized away when not needed  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-bugs
Robert Haas <robertmhaas@gmail.com> writes:
> On Tue, Jul 8, 2014 at 5:40 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Moshe Jacobson <moshe@neadwerx.com> writes:
>>> On Tue, Jul 8, 2014 at 4:40 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>>> No.  There is nothing about GROUP BY in the join removal logic.

>>> OK. Thank you. Is this something that would make sense to add?

>> Dunno.  I don't recall any previous requests for such a thing, so I'd not
>> be inclined to add it unless it can be done very cheaply (in terms of both
>> code and runtime).

> I thought this was exactly what was being discussed on the "Allowing
> join removals for more join types" thread.

No, this is a completely different thing.  The idea is that if the query
is grouping on outer-relation columns, you don't need to care if the inner
relation is unique or not, because it doesn't matter if there are multiple
matches.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Robert Haas
Date:
Subject: Re: LEFT JOINs not optimized away when not needed
Next
From: Robert Haas
Date:
Subject: Re: LEFT JOINs not optimized away when not needed