For ages I have been using MySQL 5.1.37.

Recently I noticed that this version is no longer supported in repository, so I need to upgrade mysql.

I assume that changing the version should be complicated process with changes in my.cnf, and may be with the changes in the code.


  • Which version is the most stable and preferred?
  • Which version should I use?
  • Use the latest and greatest. Simple. – gbn Jan 19 '12 at 9:51
  • 1
    If you are looking for "most stable" then pick a stable distro and use the supplied packages (eg Debian). On Windows the latest stable release is 5.5 - there is no reason not to use that as it was released in December 2010. Any major problems would be well known by now. – Jack Douglas Jan 19 '12 at 9:57
  • 1
    I am currently using MySQL-5.5.20 and it is working fine.you can go with it.It is also generally available. – Abdul Manaf Jan 19 '12 at 10:11
  • Besides the latest MySQL 5.1 and 5.5, there's also the latest MariaDB 5.2 (latest stable version: 5.2.10, released 2011-12-05). – ypercubeᵀᴹ Jan 22 '12 at 20:19

I tend to follow the following rule for existing code-base:

If it's working fine, there is no need to upgrade unless there's a specific feature you are missing.

InnoDB does get some nice performance boosts in 5.5, but if your current use-case is not seeing any issues with your install, why upgrade?

If you ran some performance tests on a development server that indicates you are getting near your limit, you could try 5.5 to see if that helps any.

For future projects, I would definitely recommend 5.5, however.

  • Thanks, moving to 5.5, should I consider changing my.cnf or code with queries? – com Jan 19 '12 at 17:50
  • I highly recommend reading the changelog for MySQL 5.5 and determining that for your use-case. Read-up on innodb performance tuning, and then come back here if you have a specific issue. – Derek Downey Jan 19 '12 at 18:05
  • Sometimes, KISS and If-it-aint-broke-dont-fix-it principles work best for most people. +1 for unless there's a specific feature you are missing. – RolandoMySQLDBA Jan 19 '12 at 20:48

You need to get away from MySQL 5.1 ASAP

MySQL 5.0 Active Support ended on December 31, 2009 - Now in Extended Support Phase Per the MySQL Support Lifecycle policy, active support for MySQL 5.0 ended on December 31, 2009. MySQL 5.0 is now in the Extended support phase.

Versions have changed rapidly since Oracle stepped in

MySQL 5.1 will soon reach its EOL (End of Life) in terms of Active support and go to Extended support (EOL : TBD). Naturally, that support is commerical. It would not hold my breath for that kind of support for the Community versions.

MySQL 5.5.20 was just released 2012-01-11 and 5.5.19 was just a month ago. As with any upgraded product, always read release notes to see what changes and improvements have come about since the previous stable release.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.