Fix interaction of triggers, partitioning, and EXPLAIN ANALYZE. Add a new EState member es_leaf_result_relations, so that the trigger code knows about ResultRelInfos created by tuple routing. Also make sure ExplainPrintTriggers knows about partition-related ResultRelInfos.
Etsuro Fujita, reviewed by Amit Langote Discussion: http://postgr.es/m/57163e18-8e56-da83-337a-22f2c0008...@lab.ntt.co.jp Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/c4b841ba6aa9252ab9dacd59d317aba8cfa9b31a Modified Files -------------- src/backend/commands/copy.c | 110 +++++++++++++++++---------------- src/backend/commands/explain.c | 15 ++++- src/backend/executor/execMain.c | 45 ++++++++++---- src/backend/executor/execUtils.c | 5 ++ src/backend/executor/nodeModifyTable.c | 1 + src/include/executor/executor.h | 1 + src/include/nodes/execnodes.h | 3 + 7 files changed, 115 insertions(+), 65 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
