1On Fri, Apr 26, 2002 at 09:11:52AM -0700, Jeremy Zawodny wrote: > I started it up and it ran for about a day before it ran into a > duplicate key error. The 3.23.47 slave hasn't hit the duplicate key > error, nor have any of our other slaves. So it is a 4.0.2 bug of > some sort.
This has been resolve, I hope. After even more tracking stuff down, I managed to isolate it to a change made in MySQL 4.0.1. The query in question was doing: INSERT INTO ... SELECT ... rather than INSERT IGNORE INTO ... SELECT ... MySQL 3.23.xx lets the first sneak by without errors even if there are duplicates. 4.0.2 does not. It stops. Since our master is 3.23 and this particular slave is 4.0.2, the two didn't agree. *sigh* I hereby declare MySQL 4.0.2 replicating from 3.23.xx to be quite stable. :-) Back to your regularly scheduled mail... Jeremy -- Jeremy D. Zawodny, <[EMAIL PROTECTED]> Technical Yahoo - Yahoo Finance Desk: (408) 349-7878 Fax: (408) 349-5454 Cell: (408) 685-5936 MySQL 3.23.47-max: up 83 days, processed 2,168,564,677 queries (300/sec. avg) --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
