For everyone who is using to a 5.1.x version. This is a bug fix release and it is up to you if you want to upgrade. Check all the fixes and changes that are listed on the release notes to see what issues are resolved and if you are affected. Most of them are about replication which we don’t use in our setup.

If you are still using a 5.0.x version I would urge you to plan a upgrade to a 5.1.x version.

I’ve compiled this version and did some tests on my servers and it worked without any problems.

Read the documentation on how to ugrade MySQL.

For everyone who is using to a 5.1.x version. This is a bug fix release and it is up to you if you want to upgrade. Check all the fixes and changes that are listed on the release notes to see what issues are resolved and if you are affected. Most of them are about replication which we don’t use in our setup. If you are still using a 5.0.x version I would urge you to plan a upgrade to a 5.1.x version.

I’ve compiled this version and did some simple tests on my servers and it worked without any problems.

Read the documentation on how to ugrade MySQL.

For all who are using to a 5.1.x version. This is a bug fix release and it is up to you if you want to upgrade. Check all the fixes and changes that are listed on the release notes to see what issues are resolved and if you are affected. Most of them are about replication and partitioning, none of which we actually use in our setup.

I’ve compiled this version and did some simple tests on my test servers and it worked without any problems.

Read the documentation on how to ugrade MySQL.

For all who are using to a 5.1.x version. This is a security and bug fix release and it is up to you if you want to upgrade. There is a three security issues mentioned in the release notes. Check all the fixes and changes that are listed on the release notes to see what issues are resolved and if you are affected.

I’ve compiled this version and did some simple tests on my test servers and it worked without any problems.

Read the documentation on how to ugrade MySQL.

MySQL released new versions of the 5.0.x community version of their database server. There are security issue releated to this release so if you still use 5.0.x I would advise you to get this version. Also note that this version is getting EOL, I would advise you to plan an upgrade to a 5.1 release.

Read more about the specifics for this release here: Changes in MySQL 5.0.91

For all who are using to a 5.1.x version. This is mostly a bug fix release and it is up to you if you want to upgrade. There is a single security issue mentioned in the release notes. Check all the fixes and changes that are listed on the release notes to see what issues are resolved and if you are affected.

I’ve compiled this version and did some simple tests on my test servers and it worked without any problems.

Please note that I’ve made some changes to the startup scripts to make sue that you are indeed running the updated version as indicated in my earlier post.

Read the documentation on how to ugrade MySQL.

For everyone who has upgraded to a 5.1.x version. This is mostly a bug fix release and it is up to you if you want to upgrade. There are no apparent security issues solved in this release. Check all the fixes and changes that are listed on the release notes to see what issues are resolved and if you are affected.

I’ve compiled this version and did some simple tests on my test servers and it worked without any problems.

Please note that I’ve made some changes to the startup scripts to make sue that you are indeed running the updated version as indicated in my earlier post.

Read the documentation on how to ugrade MySQL.

Several people have notified me of the problem they discovered when checking the version that is installed after they manually compiled MySQL from source after the binary install. The mysqld located in ‘/usr/local/mysql/bin‘ directory keeps reflecting the original installed version and not the latest source compiled version.

It took me a while to find out what was wrong here but I solved it. It is my mistake as I did not discover this earlier. The mysqld program when compiling from source is located in ‘/usr/local/mysql/libexec‘ and is properly referenced is you use the ‘mysqld_safe‘ program to start it up. The mysqld binary in ‘/usr/local/mysql/bin‘ is a left-over of the binary install procedure and is no longer used or referenced. This also means that my startup script was incorrect.

As a consequence I’ve changed the startup plist file. Please do the same by first changing the plist file and then do:

sudo launchctl unload /System/Library/LaunchDaemons/com.diymacserver.mysql.plist
sudo launchctl load /System/Library/LaunchDaemons/com.diymacserver.mysql.plist

Then the newer version should be running. You can check this by using the command:

mysqladmin version

Thanks to the vigilant users and my apologies to the others.

For everyone who has upgraded to a 5.1.x version. This is mostly a bug fix release and it is up to you if you want to upgrade. There are no apparent security issues solved in this release.

Check all the fixes and changes that are listed on the release notes to see what issues are resolved and if you are affected.

I’ve compiled this version and did some simple tests on my test servers and it worked without any problems.

Read the documentation on how to ugrade MySQL.

For everyone who has upgraded to a 5.1.x version. This is mostly a bug fix release and it is up to you if you want to upgrade. There are no apparent security issues solved in this release.

Check all the fixes and changes that are listed on the release notes to see what issues are resolved and if you are affected. Most of them are concerning replication.

I’ve compiled this version and did some simple tests on my test servers and it worked without any problems.

Read the documentation on how to ugrade MySQL.