On Wed, 2006-11-29 at 20:50 -0500, Steve Singer wrote: > Today we were doing some controlled switch-overs/move set's and encountered a > situation where Postres decided to abort the transaction executing a moveSet > due to deadlock detection. > > This left our cluster in a state where both node 1, and node 2 thought the > other one was the master/provider of the replication set. > > Has anyone else experienced this, there was other activity on the database > at the time this happened, we might even had accidently had multiple copies > of the moveset script running at once (but I don't see how both would have > been able to get the set locks).
I haven't. We make sure we are in a maintenance window and make sure that all nodes are locked down, and all transactions against them are done before doing a move set. -- Brad Nicholson 416-673-4106 Database Administrator, Afilias Canada Corp. _______________________________________________ Slony1-general mailing list [email protected] http://gborg.postgresql.org/mailman/listinfo/slony1-general
