Hi, <br><br>When I tried to deploy slony-2.0.4, there have a problem I met during slave node configuration. Maser node slon process looks hang and there is <b><span style="color: rgb(204, 0, 0);"><event pending></span></b> in pa_conninfo of sl_path table. Below is the output of that table. <br>
<br>[root@slony-r1s1-001 ~]# psql -U postgres system.db -c "select * from _slony.sl_path"<br> pa_server | pa_client | pa_conninfo | pa_connretry <br>
-----------+-----------+-----------------------------------------------------------------------------+--------------<br>2 | 1 | host=192.168.11.12 dbname=system.db user=postgres port=5432| 10<br>1 | 2 | <event pending> | 10<br>
<br><br>Here is the configuration sequence I used to setup master and slave, I used atlperl related tools to configure slon.<br><u><b>On master node:</b></u><br><ol><li>Configure and start postgresql service<br></li><li>Configure slon using slonik_init_cluster and slony_define_replication_set<br>
</li><li>Start slon service<br></li></ol><u><b>On slave node:</b></u><br><ol><li>Configure and start postgresql service</li><li>Configure slon using slonik_store_node and slonik_subscribe_set</li><li>Start slon service</li>
</ol>The incorrect configuration in sl_path will cause master node hangs and master will not generate any new SYNC event. However, <b>after about 7 hours, </b>the information in sl_path becomes correct configuration and SYNC event can be generated. <br>
<br>After check slony source, I was thinking the issue might happen during subscribeSet and add some logs in backend script slony1_funcs.sql. However, it looks like subscribeSet and enableSubscription finished successfully from slon log. I also checked slon thread info, there is no remoteListenThread_main and remoteWorkerThread_main thread comparing with normal slon process in the master node. <br>
<br>My question are:<br><ol><li>Is there any other things we can check in the slony table or logs?</li><li>Why there need to wait for 7 hours for that correct sl_path? Does there has anything block master node?</li><li>Do you think this is a configuration issue or issue inside slony source code?</li>
</ol><br>Thanks,<br>Jason<br><br>