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

From Robert Haas
Subject Re: LEFT JOINs not optimized away when not needed
Date
Msg-id CA+TgmoZ8HGpVjmnGv=UHd59b3N8KCpo-_yo1D7-GRxT8aaFsfg@mail.gmail.com
Whole thread Raw
In response to Re: LEFT JOINs not optimized away when not needed  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: LEFT JOINs not optimized away when not needed
List pgsql-bugs
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.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-bugs by date:

Previous
From: Greg Stark
Date:
Subject: Re: BUG #10911: pg_upgrade appears to lose the transaction id epoch
Next
From: Tom Lane
Date:
Subject: Re: LEFT JOINs not optimized away when not needed