Comments on: MySQL Installation and upgrade scripts. http://www.mysqlperformanceblog.com/2007/05/21/mysql-installation-and-upgrade-scripts/ Everything about MySQL Performance Tue, 02 Dec 2008 13:28:21 +0000 http://wordpress.org/?v=2.5.1 By: Dmitri Mikhailov http://www.mysqlperformanceblog.com/2007/05/21/mysql-installation-and-upgrade-scripts/#comment-129061 Dmitri Mikhailov Mon, 21 May 2007 16:27:41 +0000 http://www.mysqlperformanceblog.com/2007/05/21/mysql-installation-and-upgrade-scripts/#comment-129061 Heh, here are my 2 cents: I tried to upgrade from 4.1.19 to: 5.0.24a - fast, "check for upgrade" did not trigger table repairs (bad, varchar string comparison with trailing spaces might return different from expected results), no problems with replication, no problems with merge tables, the release just does not have the latest features/fixes. 5.0.27 - slow, with "check for upgrade" repairs, problems with auto_increment values in the replication binlogs (bug #24432) 5.0.36sp1 - slow, with "check for upgrade" repairs, no problems with large merge tables (Unable to open underlying table which is differently defined or of non-MyISAM type), no problems with replication 5.0.37 - slow, with "check for upgrade" repairs, problems with merge tables, performance problems while table is updated by PK = empty string (actially is was an application side problem, but at least this should not cause perf problems at the db side) 5.0.41 - the release is just too fresh to blindly migrate to. --- Oh, yes, SELinux had to be disabled. At the present time I decided to upgrade to 5.0.36sp1 (MySQL Enperprise) it seems to be the most stable release, it's still in the tests, who knows what bug we are going to hit next :) Heh, here are my 2 cents: I tried to upgrade from 4.1.19 to:

5.0.24a - fast, “check for upgrade” did not trigger table repairs (bad, varchar string comparison with trailing spaces might return different from expected results), no problems with replication, no problems with merge tables, the release just does not have the latest features/fixes.

5.0.27 - slow, with “check for upgrade” repairs, problems with auto_increment values in the replication binlogs (bug #24432)

5.0.36sp1 - slow, with “check for upgrade” repairs, no problems with large merge tables (Unable to open underlying table which is differently defined or of non-MyISAM type), no problems with replication

5.0.37 - slow, with “check for upgrade” repairs, problems with merge tables, performance problems while table is updated by PK = empty string (actially is was an application side problem, but at least this should not cause perf problems at the db side)

5.0.41 - the release is just too fresh to blindly migrate to.

—

Oh, yes, SELinux had to be disabled.

At the present time I decided to upgrade to 5.0.36sp1 (MySQL Enperprise) it seems to be the most stable release, it’s still in the tests, who knows what bug we are going to hit next :)

]]> By: peter http://www.mysqlperformanceblog.com/2007/05/21/mysql-installation-and-upgrade-scripts/#comment-128998 peter Mon, 21 May 2007 11:31:47 +0000 http://www.mysqlperformanceblog.com/2007/05/21/mysql-installation-and-upgrade-scripts/#comment-128998 Thank Ivo, I would have guessed there is a workaround but again I would expect this is something MySQL and RedHat could have worked among themselves - if RPM is tuned not to remove mysql user or if it is readded with same id I do not care much. I would just prefer it to work, keeping my user hat on in this case :) Thank Ivo,

I would have guessed there is a workaround but again I would expect this is something MySQL and RedHat could have worked among themselves - if RPM is tuned not to remove mysql user or if it is readded with same id I do not care much. I would just prefer it to work, keeping my user hat on in this case :)

]]> By: Ivo Teel http://www.mysqlperformanceblog.com/2007/05/21/mysql-installation-and-upgrade-scripts/#comment-128925 Ivo Teel Mon, 21 May 2007 10:47:09 +0000 http://www.mysqlperformanceblog.com/2007/05/21/mysql-installation-and-upgrade-scripts/#comment-128925 We have had simular issues with RPM, however, the missing MySQL user is related to the RPM itself. It removes the mysql user on deinstallation and for some reason doesn't readd it. This only occurs for upgrades, if you remove it and then reinstall (the newer version) it works just fine. Nowadays we just remove the old version first and immediate install the newer version and move back the configuration. We have had simular issues with RPM, however, the missing MySQL user is related to the RPM itself. It removes the mysql user on deinstallation and for some reason doesn’t readd it. This only occurs for upgrades, if you remove it and then reinstall (the newer version) it works just fine.

Nowadays we just remove the old version first and immediate install the newer version and move back the configuration.

]]>