Tue Sep 9 14:30:27 PDT 2008
- Previous message: [Slony1-commit] slony1-engine/src/slon remote_worker.c
- Next message: [Slony1-commit] slony1-engine config.h.in
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Update of /home/cvsd/slony1/slony1-engine/src/slon In directory main.slony.info:/tmp/cvs-serv21140 Modified Files: Tag: REL_1_2_STABLE remote_worker.c Log Message: Fix to bug #56 http://www.slony.info/bugzilla/show_bug.cgi?id=56 COPY_SET was using storeTrigger() rather than storeTrigger_int(), which means that during the subscription, STORE TRIGGER events would proliferate across the cluster rather than being confined to the new subscriber. Index: remote_worker.c =================================================================== RCS file: /home/cvsd/slony1/slony1-engine/src/slon/remote_worker.c,v retrieving revision 1.124.2.34 retrieving revision 1.124.2.35 diff -C2 -d -r1.124.2.34 -r1.124.2.35 *** remote_worker.c 20 Jun 2008 22:19:10 -0000 1.124.2.34 --- remote_worker.c 9 Sep 2008 21:30:25 -0000 1.124.2.35 *************** *** 2980,2984 **** { slon_mkquery(&query1, ! "select %s.storeTrigger(%d, '%q'); ", rtcfg_namespace, tab_id, PQgetvalue(res2, tupno2, 0)); if (query_execute(node, loc_dbconn, &query1) < 0) --- 2980,2984 ---- { slon_mkquery(&query1, ! "select %s.storeTrigger_int(%d, '%q'); ", rtcfg_namespace, tab_id, PQgetvalue(res2, tupno2, 0)); if (query_execute(node, loc_dbconn, &query1) < 0)
- Previous message: [Slony1-commit] slony1-engine/src/slon remote_worker.c
- Next message: [Slony1-commit] slony1-engine config.h.in
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-commit mailing list