pgsql: Fix valgrind issue in commit 05c8482f7f.

From: Amit Kapila <akapila(at)postgresql(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Fix valgrind issue in commit 05c8482f7f.
Date: 2021-03-10 04:43:14
Message-ID: E1lJqgk-00060h-0P@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Fix valgrind issue in commit 05c8482f7f.

Initialize other newly added variables in max_parallel_hazard_context via
is_parallel_safe() because we don't check the parallel-safety of target
relations in that function.

Reported-by: Tom Lane as per buildfarm
Author: Amit Kapila
Discussion: https://postgr.es/m/2060179.1615347455@sss.pgh.pa.us

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/e4e87a32cc5559303068b148bd4aa6a39b8f44a1

Modified Files
--------------
src/backend/optimizer/util/clauses.c | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Thomas Munro 2021-03-10 04:52:01 pgsql: pgbench: Synchronize client threads.
Previous Message Amit Kapila 2021-03-10 04:16:35 Re: pgsql: Enable parallel SELECT for "INSERT INTO ... SELECT ...".