Upgrading to MySQL 5.0.40 on RHEL and CentOS

May 5, 2007 by · 2 Comments 

Another month brings another Enterprise-only release of the MySQL database server under the "Monthly Rapid Update" program. As with the last few Enterprise releases, I've built RHEL-style 32- & 64-bit binary packages for all of the community users out there so that they can keep their systems up-to-date.

The spec file is unmodified from my release of 5.0.38 but the source has been updated to 5.0.40. If you would like to download the src.rpm to compile yourself or simply to look and see what I've done, feel free to use the link at the bottom of this post.

If you are a user of my yum repository then you can simply run "yum update" and your system will download this release. If not, I would suggest that you check out the link titled "Yum Repository" at the top of the page as it can really make updating your system a LOT easier. Have fun!

MySQL 5.0.40 Release Notes

Update (9/24/2009): Packages deleted, use the yum repository instead.


2 Responses to “Upgrading to MySQL 5.0.40 on RHEL and CentOS”
  1. There is a problem upgrading a replication setup from versions prior to 5.0.36 to 5.0.40. Seems like there was a bug fix in the replication code that makes the replication deliberately incompatible between the versions. When trying to start replication on servers with incompatible replication you will see the following message

    Slave: According to the master's version ('5.0.34-enterprise-gpl-log'), it is probable that master suffers from this bug: http://bugs.mysql.com/bug.php?id=24432 and thus replicating the current binary log event may make the slave's data become different from the master's data. To take no risk, slave refuses to replicate this event and stops. We recommend that all updates be stopped on the master and slave, that the data of both be manually synchronized, that master's binary logs be deleted, that master be upgraded to a version at least equal to '5.0.38'.

    The correct way of upgrading a live replication setup to the new version would be to upgrade the slave to 5.0.38, promote it to master, upgrade master to 5.0.40 and reseed it as slave. Promote the slave and upgrade the 5.0.38 system to 5.0.40.

  2. Jason says:

    Good info. I didn't run into that with my replicating pairs because all of my servers were already running 5.0.38.

Speak Your Mind

Tell us what you're thinking...
and oh, if you want a pic to show with your comment, go get a gravatar!


Note: This post is over 5 years old. You may want to check later in this blog to see if there is new information relevant to your comment.

By submitting a comment here you grant this site a perpetual license to reproduce your words and name/web site in attribution. Use of a non-personal web site or blog in the "Web Site" field and/or leaving a comment that is off-topic or inappropriate may result in the comment being edited or removed at the discretion of the site owner.