From 22b73d3cb0b5bb4c141421f98dd67f091dda3c20 Mon Sep 17 00:00:00 2001 From: Heikki Linnakangas Date: Fri, 23 Oct 2020 09:30:08 +0300 Subject: [PATCH] Fix initialization of es_result_relations in EvalPlanQualStart(). Thinko in commit 1375422c782. EvalPlanQualStart() was mistakenly resetting the parent EState's es_result_relations, when it should initialize the field in the child EPQ EState it just created. That was clearly wrong, but it didn't cause any ill effects, because es_result_relations is currently not used after the ExecInit* phase. Author: Amit Langote Discussion: https://www.postgresql.org/message-id/CA%2BHiwqFEuq8AAAmxXsTDVZ1r38cHbfYuiPQx_%3DYyKe2DC-6q4A%40mail.gmail.com --- src/backend/executor/execMain.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/backend/executor/execMain.c b/src/backend/executor/execMain.c index aea0479448..7179f589f9 100644 --- a/src/backend/executor/execMain.c +++ b/src/backend/executor/execMain.c @@ -2693,7 +2693,7 @@ EvalPlanQualStart(EPQState *epqstate, Plan *planTree) * ResultRelInfos needed by subplans are initialized from scratch when the * subplans themselves are initialized. */ - parentestate->es_result_relations = NULL; + rcestate->es_result_relations = NULL; /* es_trig_target_relations must NOT be copied */ rcestate->es_top_eflags = parentestate->es_top_eflags; rcestate->es_instrument = parentestate->es_instrument;