aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/execMain.c
diff options
context:
space:
mode:
authorRobert Haas <rhaas@postgresql.org>2018-02-08 14:29:05 -0500
committerRobert Haas <rhaas@postgresql.org>2018-02-08 14:29:05 -0500
commite44dd84325c277fd031b9ef486c51a0946c7d3a0 (patch)
treea501ae2a890898c23dcac6a791fe08299ed9b3c6 /src/backend/executor/execMain.c
parent88fdc7006018b92d6ec92c54b3819764703daaba (diff)
downloadpostgresql-e44dd84325c277fd031b9ef486c51a0946c7d3a0.tar.gz
postgresql-e44dd84325c277fd031b9ef486c51a0946c7d3a0.zip
Avoid listing the same ResultRelInfo in more than one EState list.
Doing so causes EXPLAIN ANALYZE to show trigger statistics multiple times. Commit 2f178441044be430f6b4d626e4dae68a9a6f6cec seems to be to blame for this. Amit Langote, revieed by Amit Khandekar, Etsuro Fujita, and me.
Diffstat (limited to 'src/backend/executor/execMain.c')
-rw-r--r--src/backend/executor/execMain.c7
1 files changed, 5 insertions, 2 deletions
diff --git a/src/backend/executor/execMain.c b/src/backend/executor/execMain.c
index 410921cc408..5d3e923cca3 100644
--- a/src/backend/executor/execMain.c
+++ b/src/backend/executor/execMain.c
@@ -1413,8 +1413,11 @@ ExecGetTriggerResultRel(EState *estate, Oid relid)
rInfo++;
nr--;
}
- /* Third, search through the leaf result relations, if any */
- foreach(l, estate->es_leaf_result_relations)
+ /*
+ * Third, search through the result relations that were created during
+ * tuple routing, if any.
+ */
+ foreach(l, estate->es_tuple_routing_result_relations)
{
rInfo = (ResultRelInfo *) lfirst(l);
if (RelationGetRelid(rInfo->ri_RelationDesc) == relid)