Thu Aug 4 13:28:26 PDT 2011
- Previous message: [Slony1-bugs] [Bug 173] Slonik ABORT command
- Next message: [Slony1-bugs] [Bug 228] 'drop node' in a try block
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=228 Summary: 'drop node' in a try block Product: Slony-I Version: devel Platform: PC OS/Version: Linux Status: NEW Severity: enhancement Priority: low Component: slonik AssignedTo: slony1-bugs at lists.slony.info ReportedBy: ssinger at ca.afilias.info CC: slony1-bugs at lists.slony.info Estimated Hours: 0.0 In doing some testing against the 2.1.0 beta I tried executing some slonik code like try { drop node(id=3, event node=1); } on error { echo "node already gone"; } store node(id=3, event node=1); A script like this will fail in the current 2.1.0 betas and this shouldn't surprise anyone who has read about the new features in 2.1.0 A drop node requires that the cluster be somewhat caught up (at least to the extent that any events from the drop'd node that have been confirmed elsewhere are confirmed everywhere). This means that drop node has an implicit 'wait for event' before it. However you can't have 'wait for events' inside a try block. -- Configure bugmail: http://www.slony.info/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. You are the assignee for the bug.
- Previous message: [Slony1-bugs] [Bug 173] Slonik ABORT command
- Next message: [Slony1-bugs] [Bug 228] 'drop node' in a try block
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list