Glyn Astill glynastill at yahoo.co.uk
Thu Nov 8 09:31:45 PST 2012
Hi Guys,

I was just taking a look at the changes to lockset() between 2.0 and 2.1 and noticed it now uses a lock on the row in sl_set rather than a table lock on sl_config_lock.

I was wondering, does this now make it possible to do something along the lines of:

TRY {
LOCK SET ( ID = 1, ORIGIN = 1);
LOCK SET ( ID = 2, ORIGIN = 1);
}
ON ERROR ( blah }
MOVE SET ( ID = 1, OLD ORIGIN = 1, NEW ORIGIN = 2);
WAIT FOR EVENT (ORIGIN = 1, CONFIRMED = ALL, WAIT ON = 1, TIMEOUT = 0);
MOVE SET ( ID = 2, OLD ORIGIN = 1, NEW ORIGIN = 2);
WAIT FOR EVENT (ORIGIN = 1, CONFIRMED = ALL, WAIT ON = 1, TIMEOUT = 0);

(Or even wrap the move sets in a try too?)

The reason I ask is we're currently using 2.0.7 and when we move a bunch of sets between nodes it'd be ideal if they were all locked before they were moved.

Sorry if I've got the wrong end of the stick here, or this has already been answered somewhere, I did do a good search before posting!

Thanks
Glyn
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slony.info/pipermail/slony1-general/attachments/20121108/5b888eff/attachment.htm 


More information about the Slony1-general mailing list