Commit 22b73d3c authored by Heikki Linnakangas's avatar Heikki Linnakangas

Fix initialization of es_result_relations in EvalPlanQualStart().

Thinko in commit 1375422c. 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
parent 783f0cc6
...@@ -2693,7 +2693,7 @@ EvalPlanQualStart(EPQState *epqstate, Plan *planTree) ...@@ -2693,7 +2693,7 @@ EvalPlanQualStart(EPQState *epqstate, Plan *planTree)
* ResultRelInfos needed by subplans are initialized from scratch when the * ResultRelInfos needed by subplans are initialized from scratch when the
* subplans themselves are initialized. * subplans themselves are initialized.
*/ */
parentestate->es_result_relations = NULL; rcestate->es_result_relations = NULL;
/* es_trig_target_relations must NOT be copied */ /* es_trig_target_relations must NOT be copied */
rcestate->es_top_eflags = parentestate->es_top_eflags; rcestate->es_top_eflags = parentestate->es_top_eflags;
rcestate->es_instrument = parentestate->es_instrument; rcestate->es_instrument = parentestate->es_instrument;
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment