We have changed the release model so that instead of focusing on quality and features our release is now defined by timeliness and features. Quality is not regarded to be that important.

and

Zero critical bugs is impossible: Sure, zero bugs is desirable. And at times, we internally glorify MySQL’s past, with “production level alpha releases”. Those were the days, but those days also had less complex and less interwoven features, and fewer developers to manage.

I wonder where MySQL is headed.

So as Monty says, you are better off not upgrading to version 5.1 if you do not plan to use its new features, atleast not without testing it for a few weeks.

Links:
Oops, we did it again (MySQL 5.1 released as GA with crashing bugs)
Why You Want to Switch to MySQL 5.1
MySQL 5.1 Stability

Related posts:

1. How to skip MySQL replication counter There are such times when MySQL replication stops when you...

A simple way out of this is to run the missing DDLs on the slave and push the counter by a step. This is not recommended as this might cause data inconsistency.

Use the below sql to skip the counter by 1.

SET GLOBAL SQL_SLAVE_SKIP_COUNTER = 1; START SLAVE;

Just remember to use the value 1 for any SQL statement that does not use AUTO_INCREMENT or LAST_INSERT_ID(), otherwise you will need to use the value 2. Statements that use AUTO_INCREMENT or LAST_INSERT_ID() take up 2 events in the binary log.

To skip lots of duplicate errors, you can set this in my.cnf

slave-skip-errors = 1062

No related posts.