Thu Nov 18 08:24:23 PST 2004
- Previous message: [Slony1-general] Error when creating a 2nd set. :(
- Next message: [Slony1-general] Slonik 'EXIT' command not closing database connection properly
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jan Wieck a ?crit : > On 11/17/2004 10:40 AM, Dr. St?phane Schildknecht wrote: > >> wait for event (origin = 1, confirmed = 1); > > > you want that event to be confirmed by node 2, not its own origin. OK ! >> subscribe set ( id = 2, PROVIDER = 1, receiver = 2, forward = no ); >> merge set ( id = 1, add id = 2, origin = 1); > > And this is a secure way to screw up the cluster in versions prior to > 1.0.5. The merge set can only be done AFTER node 2 has sucessfully > subscribed and copied the data. Does that mean I have to put a "wait for event" between the subscribe and merge commands, also ? I'll try that. > Sorry, but Slony is not a fire-and-forget system yet ;-) No, but the community is so kind and reactiv, that I won't bother having to do things by myself :-p Thanks a lot S at S -- St?phane SCHILDKNECHT LINAGORA 30 rue Saint Augustin 75002 PARIS Tel : +33(0)1 58 18 68 28 fax : +33(0)1 58 18 68 29 http://www.linagora.com
- Previous message: [Slony1-general] Error when creating a 2nd set. :(
- Next message: [Slony1-general] Slonik 'EXIT' command not closing database connection properly
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list