> From: Steve Singer <[email protected]> >To: Glyn Astill <[email protected]> >Cc: slony <[email protected]> >Sent: Friday, 9 November 2012, 18:13 >Subject: Re: [Slony1-general] Lock set behaviour difference between 2.0 and 2.1 > > >Why can't you just do > >try { >LOCK SET ( ID = 1, ORIGIN = 1); >LOCK SET ( ID = 2, ORIGIN = 1); >MOVE SET ( ID = 1, OLD ORIGIN = 1, NEW ORIGIN = 2); >MOVE SET ( ID = 2, OLD ORIGIN = 1, NEW ORIGIN = 2); >} >WAIT FOR EVENT(ORIGIN=1, CONFIRMED=ALL...) > >(I haven't actually tested the above but I think it will work in cases >were both sets are on the same origin). > >
Hi Steve, I've just tried the above on 2.1.2 and I get the same error message as on 2.0.7 when I try to lock the second set: "cannot lock set - admin connection already in transaction" I'm guessing "lock set" and "move set" have to be run consecutively? _______________________________________________ Slony1-general mailing list [email protected] http://lists.slony.info/mailman/listinfo/slony1-general
