I have been running circular replication between two servers for a couple of years without problems. One server generates even auto-increment values, the other odd.
Since upgrading to sql version 5.1.61 a few weeks ago I have twice had 'Duplicate Entry' errors (on the auto-increment primary key) during replication.
In each case, the duplicate entry error happened when using an 'insert ... select' statement, selecting from a temp/memory table into myisam. Null values were inserted for the primary key (ie 'select null, field2, field3 from temp_table...').
I am using statement based replication.
The upgrade may be a coincidence of course.... but suspicious ... I cannot think how my code could 'legitimately' create this error, so should i report this as a possible bug? It seems similar in nature to
http://bugs.mysql.com/bug.php?id=45677 , though it cannot be exactly the same bug
Can anyone shed any light on this?