Re: pgsql: Add some regression tests that exercise hash join code.

From: Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-committers <pgsql-committers(at)postgresql(dot)org>
Subject: Re: pgsql: Add some regression tests that exercise hash join code.
Date: 2017-12-05 20:05:44
Message-ID: CAEepm=1YcFGWUJfU77c3cuC=SeBU0Yo_wBD8jFUMBUMkhymhHQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Wed, Dec 6, 2017 at 8:03 AM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> On 2017-12-05 12:59:21 +1300, Thomas Munro wrote:
>> src/backend/commands/explain.c | 58 ++++++++++++++------
>
> This didn't actually include nodeHash.h, ...

Ugh, I'd lost -Werror from my COPT. Back in there it goes.

> Pushed, thanks for the patch. Let's see what the buildfarm says...

Thank you. I'm keeping an eye on it.

By the way, the current coding of ExecSortRetrieveInstrumentation()
and now also ExecHashRetrieveInstrumentation() is wrong in the case of
rescans, since they get called multiple times but are written in a way
that assumes they'll be called only once:

https://www.postgresql.org/message-id/CAA4eK1JBj4YCEQKeTua5%3DBMXy7zW7zNOvoXomzBP%3Dkb_aqMF7w%40mail.gmail.com

Amit's patch would move ExecParallelRetrieveInstrumentation() so that
they are called only once, so that would fix that problem without any
change to this code. More over on that thread.

--
Thomas Munro
http://www.enterprisedb.com

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Eisentraut 2017-12-05 20:42:45 pgsql: doc: Update memory requirements for FOP
Previous Message Tom Lane 2017-12-05 19:45:59 Re: pgsql: PL/Python: Fix potential NULL pointer dereference