From: Simon Riggs <simon@2ndQuadrant.com>
Date: Tue, 28 Nov 2017 09:37:22 +0000 (+0000)
Subject: Set es_output_cid in replication worker
X-Git-Tag: REL_10_2~110
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=7015bb38949a44849b7a2e6c139700d20d82858b;p=postgresql

Set es_output_cid in replication worker

Allows triggers to operate correctly

Author: Petr Jelinek <petr.jelinek@2ndquadrant.com>
Reported-by: Konstantin Knizhnik <k.knizhnik@postgrespro.ru>
---

diff --git a/src/backend/replication/logical/worker.c b/src/backend/replication/logical/worker.c
index eedc3a8816..e46a62e199 100644
--- a/src/backend/replication/logical/worker.c
+++ b/src/backend/replication/logical/worker.c
@@ -204,6 +204,8 @@ create_estate_for_relation(LogicalRepRelMapEntry *rel)
 	estate->es_num_result_relations = 1;
 	estate->es_result_relation_info = resultRelInfo;
 
+	estate->es_output_cid = GetCurrentCommandId(true);
+
 	/* Triggers might need a slot */
 	if (resultRelInfo->ri_TrigDesc)
 		estate->es_trig_tuple_slot = ExecInitExtraTupleSlot(estate);