Craig Ringer wrote:
On Mon, 2009-06-22 at 22:20 -0400, Gerry Reno wrote:
Here is a link that describes the technique:
http://www.onlamp.com/pub/a/onlamp/2006/04/20/advanced-mysql-replication.html?page=1
Ah. You were referring to multiple-master replication, and your
reference to setting non-overlapping sequences referred to avoiding
collisions caused by inserts on two different masters. Yes, using
non-overlapping allocation ranges for sequences is indeed one way to
handle that, but it's not actually related to what I was talking about
anyway.
What I was referring to in the parent post was an issue with
statement-based replication of concurrent statements sharing a sequence.
It's completely unrelated; both statements are running on the SAME
server (master) and replicating to the slave.
I think mysql actually turns off autoincrement on the slave inserts and just plugs them in. Since the masters have non-overlapping allocation this assures that the slaves will have proper sequences as well.
Regards,
Gerry