Re: Performance improvement for joins where outer side is unique

From: David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Performance improvement for joins where outer side is unique
Date: 2015-12-16 00:27:41
Views: Raw Message | Whole Thread | Download mbox
Lists: pgsql-hackers

On 25 August 2015 at 17:25, David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>

> On 24 August 2015 at 14:29, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> writes:
>> > I have to admit I don't much like it either, originally I had this as an
>> > extra property that was only seen in EXPLAIN VERBOSE.
>> Seems like a reasonable design from here.
> The attached patch has the format in this way.

I've attached a rebased patch against current master as there were some
conflicts from the recent changes to LATERAL join.

On reviewing the patch again I was reminded that the bulk of the changes in
the patch are in analyzejoins.c. These are mostly just a refactor of the
current code to make it more reusable. The diff looks a bit more scary than
it actually is.

David Rowley
PostgreSQL Development, 24x7 Support, Training & Services

Attachment Content-Type Size
unique_joins_16-12-2015_7a290ab1.patch application/octet-stream 75.3 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2015-12-16 01:20:27 Re: [PATCH] Equivalence Class Filters
Previous Message Simon Riggs 2015-12-16 00:26:49 Re: [PATCH] Equivalence Class Filters