Re: Removing INNER JOINs

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Atri Sharma <atri(dot)jiit(at)gmail(dot)com>
Cc: David Rowley <dgrowleyml(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Mart Kelder <mart(at)kelder31(dot)nl>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Removing INNER JOINs
Date: 2014-12-07 09:42:52
Message-ID: CA+U5nM+PYz8tC41qUNJM3JwJ+ppgxwk_sUtm+OJOjjNhEBLgDw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 4 December 2014 at 12:24, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> On 3 December 2014 at 12:18, Atri Sharma <atri(dot)jiit(at)gmail(dot)com> wrote:
>
>> So the planner keeps all possibility satisfying plans, or it looks at the
>> possible conditions (like presence of foreign key for this case, for eg) and
>> then lets executor choose between them?
>
> I'm suggesting the planner keeps 2 plans: One with removable joins,
> one without the removable joins.

I only just noticed the thread moved on while I was flying.

So it looks Tom and I said the same thing, or close enough for me to +1 Tom.

Another idea would be to only skip Hash and Merge Joins, since the
tests for those are fairly easy to put into the Init call. That sounds
slightly easier than the proposal with the Option/Choice/Switch node.

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Guillaume Lelarge 2014-12-07 12:03:58 Misunderstanding on the FSM README file
Previous Message Bruce Momjian 2014-12-07 03:43:46 Re: Testing DDL deparsing support