aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/execUtils.c
diff options
context:
space:
mode:
authorHeikki Linnakangas <heikki.linnakangas@iki.fi>2020-10-14 11:41:40 +0300
committerHeikki Linnakangas <heikki.linnakangas@iki.fi>2020-10-14 11:41:40 +0300
commita04daa97a4339c38e304cd6164d37da540d665a8 (patch)
treefe77d311bc7aa4ad87db41730a3ba2cb7d1a5313 /src/backend/executor/execUtils.c
parent178f2d560dde05b356ab2f586b8bc62514f454aa (diff)
downloadpostgresql-a04daa97a4339c38e304cd6164d37da540d665a8.tar.gz
postgresql-a04daa97a4339c38e304cd6164d37da540d665a8.zip
Remove es_result_relation_info from EState.
Maintaining 'es_result_relation_info' correctly at all times has become cumbersome, especially with partitioning where each partition gets its own result relation info. Having to set and reset it across arbitrary operations has caused bugs in the past. This changes all the places that used 'es_result_relation_info', to receive the currently active ResultRelInfo via function parameters instead. Author: Amit Langote Discussion: https://www.postgresql.org/message-id/CA%2BHiwqGEmiib8FLiHMhKB%2BCH5dRgHSLc5N5wnvc4kym%2BZYpQEQ%40mail.gmail.com
Diffstat (limited to 'src/backend/executor/execUtils.c')
-rw-r--r--src/backend/executor/execUtils.c1
1 files changed, 0 insertions, 1 deletions
diff --git a/src/backend/executor/execUtils.c b/src/backend/executor/execUtils.c
index 6d8c112e2fe..071a0007ebc 100644
--- a/src/backend/executor/execUtils.c
+++ b/src/backend/executor/execUtils.c
@@ -125,7 +125,6 @@ CreateExecutorState(void)
estate->es_result_relations = NULL;
estate->es_opened_result_relations = NIL;
- estate->es_result_relation_info = NULL;
estate->es_tuple_routing_result_relations = NIL;
estate->es_trig_target_relations = NIL;