Re: Removing INNER JOINs

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Mart Kelder <mart(at)kelder31(dot)nl>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Removing INNER JOINs
Date: 2014-11-30 19:40:20
Message-ID: CAApHDvrqt2cO0UMC1Hm1L1bPetxPy8PZuzPBoVEbTvsf7kVotQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 1 December 2014 at 06:51, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> David Rowley <dgrowleyml(at)gmail(dot)com> writes:
> > I see this is quite a fundamental change to how things currently work and
> > it could cause planning to take place during the execution of PREPAREd
> > statements, which might not impress people too much, but it would
> certainly
> > fix the weird anomalies that I'm currently facing by trimming the plan at
> > executor startup. e.g left over Sort nodes after a MergeJoin was removed.
>
> > It would be interesting to hear Tom's opinion on this.
>
> Another question is what effect this has on EXPLAIN; there's basically
> no way you can avoid lying to the user about what's going to happen at
> runtime.
>
>
One of us must be missing something here. As far as I see it, there are no
lies told, the EXPLAIN shows exactly the plan that will be executed. All of
the regression tests I've added rely on this.

Regards

David Rowley

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2014-11-30 20:37:35 Re: [HACKERS] BUG #12070: hstore extension: hstore_to_json_loose produces invalid JSON
Previous Message Pavel Stehule 2014-11-30 19:17:28 Re: TODO item: Accept aliases for values in ROW(...) constructor