Fri Jul 9 06:21:52 PDT 2010
- Previous message: [PATCH] Fix for Bug #120 Call enableNode as part of the CLONE NODE processing. This will start the worker thread for the cloned node.
- Next message: [Slony1-patches] fix for bug #120
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Steve Singer wrote: Attached is a revised version of the patch updated after I talked to Jan about it. Instead we just call rtcfg_enableNode() from the CLONE_NODE processing block. In my testing I am noticing that after a CLONE FINISH I sometimes get duplicate key violations trying to insert into sl_event, (I also see these with CLONE FINISH without the patch). I'm thinking that is due to another issue with clone node not bug120. > The attached patch tries to fix bug # 120. > > As it is longer than a trivial patch someone else should look it over > before I apply it. > > Thanks > > http://github.com/ssinger/slony/commit/c36394565260d751a493abdfa2b61fb90f2912b3 > > > > > ------------------------------------------------------------------------ > > _______________________________________________ > Slony1-patches mailing list > Slony1-patches at lists.slony.info > http://lists.slony.info/mailman/listinfo/slony1-patches -- Steve Singer Afilias Canada Data Services Developer 416-673-1142 -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Fix-for-Bug-120.patch Type: text/x-patch Size: 0 bytes Desc: not available Url : http://lists.slony.info/pipermail/slony1-patches/attachments/20100709/21c4d8b5/attachment.bin
- Previous message: [PATCH] Fix for Bug #120 Call enableNode as part of the CLONE NODE processing. This will start the worker thread for the cloned node.
- Next message: [Slony1-patches] fix for bug #120
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-patches mailing list