pgsql: Fix NULL handling in multi-batch Parallel Hash Left Join.

From: Thomas Munro <tmunro(at)postgresql(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Fix NULL handling in multi-batch Parallel Hash Left Join.
Date: 2018-11-02 22:07:50
Message-ID: E1gIhba-0006jN-AI@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Fix NULL handling in multi-batch Parallel Hash Left Join.

NULL keys in left joins were skipped when building batch files.
Repair, by making the keep_nulls argument to ExecHashGetHashValue()
depend on whether this is a left outer join, as we do in other
paths.

Bug #15475. Thinko in 1804284042e. Back-patch to 11.

Reported-by: Paul Schaap
Diagnosed-by: Andrew Gierth
Dicussion: https://postgr.es/m/15475-11a7a783fed72a36%40postgresql.org

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/1ce4a807e25bcd726e34b8d3ba0338e9299f9a87

Modified Files
--------------
src/backend/executor/nodeHashjoin.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Thomas Munro 2018-11-02 22:08:19 pgsql: Fix NULL handling in multi-batch Parallel Hash Left Join.
Previous Message Bruce Momjian 2018-11-02 17:05:47 pgsql: docs: adjust simpler language for NULL return from ANY/ALL