Postgres Pro
Downloads
Home   >   mailing lists

Re: Performance improvement for joins where outer side is unique - Mailing list pgsql-hackers

From David Rowley
Subject Re: Performance improvement for joins where outer side is unique
Date
Msg-id CAKJS1f8MpcL4_oS+n-vmnisd_8OMuZR2vyLETOF7ABSLk_iNZg@mail.gmail.com
Whole thread Raw
In response to Re: Performance improvement for joins where outer side is unique  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: Performance improvement for joins where outer side is unique  (Michael Paquier <michael.paquier@gmail.com>)
Re: Performance improvement for joins where outer side is unique  (Tomas Vondra <tomas.vondra@2ndquadrant.com>)
List pgsql-hackers
Tree view
On 17 December 2015 at 19:11, Simon Riggs <simon@2ndquadrant.com> wrote:
On 17 December 2015 at 00:17, Tomas Vondra <tomas.vondra@2ndquadrant.com> wrote:
I'd go with match_first_tuple_only.

+1

unique_inner is a state that has been detected, match_first_tuple_only is the action we take as a result. 


Ok great. I've made it so in the attached. This means the comment in the join code where we perform the skip can be a bit less verbose and all the details can go in where we're actually setting the match_first_tuple_only to true.

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

pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: Combining Aggregates
Next
From: Fabien COELHO
Date:
Subject: Re: extend pgbench expressions with functions