Re: Performance improvement for joins where outer side is unique

From: David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>
To: Antonin Houska <ah(at)cybertec(dot)at>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Performance improvement for joins where outer side is unique
Date: 2017-01-26 11:39:26
Message-ID: CAKJS1f_iug=GfB3k0CHOha08wFiuM=XRPNx89s-wCMjd6auR6A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 26 January 2017 at 04:56, Antonin Houska <ah(at)cybertec(dot)at> wrote:
> I suspect that "inner" and "outer" relation / tuple are sometimes confused in
> comments:
>
>
> * analyzejoins.c:70
>
> "searches for subsequent matching outer tuples."
>
>
> * analyzejoins.c:972
>
> /*
> * innerrel_is_unique
> * Check for proofs which prove that 'innerrel' can, at most, match a
> * single tuple in 'outerrel' based on the join condition in
> * 'restrictlist'.
> */
>
>
> * relation.h:1831
>
> bool inner_unique; /* inner side of join matches no more than one
> * outer side tuple */

Thanks for looking over the patch. I believe I've fixed all those now.
I'm not too surprised I got some wrong, after all, I did mess up the
subject of this email too! Which did cause quite a bit of confusion.

--
David Rowley http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Kyotaro HORIGUCHI 2017-01-26 12:11:22 Re: Floating point comparison inconsistencies of the geometric types
Previous Message David Rowley 2017-01-26 11:37:20 Re: Performance improvement for joins where outer side is unique