rdelaage
/
postgresql
mirror of https://git.postgresql.org/git/postgresql.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

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
This commit is contained in:
Amit Kapila 2021-03-10 10:04:20 +05:30
parent 05c8482f7f
commit e4e87a32cc
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
src/backend/optimizer/util/clauses.c
View File

@ -614,9 +614,10 @@ is_parallel_safe(PlannerInfo *root, Node *node)
context.max_hazard = PROPARALLEL_SAFE;
context.max_interesting = PROPARALLEL_RESTRICTED;
context.safe_param_ids = NIL;
context.command_type = node != NULL && IsA(node, Query) ?
castNode(Query, node)->commandType : CMD_UNKNOWN;
context.planner_global = root->glob;
/* We don't need to evaluate target relation's parallel-safety here. */
context.target_rte = NULL;
context.command_type = CMD_UNKNOWN;
context.planner_global = NULL;
/*
* The params that refer to the same or parent query level are considered