catch config reload errors in MtmExecutor too

Author: kelvich

src/bgwpool.c

@@ -73,6 +73,11 @@ BgwPoolMainLoop(BgwPool* pool)
 	pqsignal(SIGTERM, BgwShutdownHandler);
 	pqsignal(SIGHUP, PostgresSigHupHandler);
 
+	// XXX: probably we should add static variable that signalizes that
+	// we are between pool->active += 1 and pool->active -= 1, so if
+	// we face an ERROR outside of PG_TRY we can decrement pool->active
+	// from on_shem_exit_hook
+
 	BackgroundWorkerUnblockSignals();
 	BackgroundWorkerInitializeConnectionByOid(pool->db_id, pool->user_id, 0);
 	ActivePortal = &fakePortal;

src/pglogical_apply.c

@@ -1473,6 +1473,7 @@ MtmExecutor(void* work, size_t size, MtmReceiverContext *receiver_ctx)
 	top_context = MemoryContextSwitchTo(MtmApplyContext);
 	replorigin_session_origin = InvalidRepOriginId;
 
+	PG_TRY();
 
 	AcceptInvalidationMessages();
 	if (!receiver_mtm_cfg_valid)
@@ -1494,7 +1495,6 @@ MtmExecutor(void* work, size_t size, MtmReceiverContext *receiver_ctx)
 	ResetAllOptions();
 	CommitTransactionCommand();
 
-    PG_TRY();
     {    
 		bool inside_transaction = true;
         do {