start resolver after monitor started dmq suscriptions

Author: kelvich

src/resolver.c

@@ -400,6 +400,7 @@ scatter_status_requests(MtmConfig *mtm_cfg)
 				MtmInitMessage(&msg, MSG_POLL_REQUEST);
 				strncpy(msg.gid, tx->gid, GIDSIZE);
 
+				// XXX
 				MtmLock(LW_SHARED);
 				dest_id = Mtm->dmq_dest_ids[node_id - 1];
 				MtmUnlock();

src/state.c

@@ -1221,7 +1221,7 @@ MtmMonitor(Datum arg)
 				user_id;
 	MtmConfig  *mtm_cfg = NULL;
 	BackgroundWorkerHandle *receivers[MTM_MAX_NODES];
-	BackgroundWorkerHandle *resolver;
+	BackgroundWorkerHandle *resolver = NULL;
 
 	memset(receivers, '\0', MTM_MAX_NODES * sizeof(BackgroundWorkerHandle *));
 
@@ -1297,11 +1297,6 @@ MtmMonitor(Datum arg)
 								  pubsub_change_cb,
 								  (Datum) 0);
 
-	/* Now start all other necessary workers */
-
-	/* Launch resolver */
-	resolver = ResolverStart(db_id, user_id);
-
 	dmq_stream_subscribe("txreq");
 
 	for (;;)
@@ -1357,6 +1352,11 @@ MtmMonitor(Datum arg)
 			config_valid = true;
 		}
 
+		/* Launch resolver after we added dmq destinations */
+		// XXX: that's because of current use of Mtm->dmq_dest_ids[]
+		if (resolver == NULL)
+			resolver = ResolverStart(db_id, user_id);
+
 		check_status_requests(mtm_cfg);
 
 		rc = WaitLatch(MyLatch,