Percona Server 5.5.21-25.1 released!


Percona is glad to announce the release of Percona Server 5.5.21-25.1 on March 30, 2012 (Downloads are available here and from the Percona Software Repositories).

Based on MySQL 5.5.21, including all the bug fixes in it, Percona Server 5.5.21-25.1 is now the current stable release in the 5.5 series. All of Percona‘s software is open-source and free, all the details of the release can be found in the 5.5.21-25.1 milestone at Launchpad.

We are doing another release based on MySQL 5.5.21 as we have a couple of important bug fixes that we wish to make available.

Bugs Fixed:

  • Fixed a memory corruption regression introduced in 5.5.18-23.0. Bug fixed #915814 (Alexey Kopytov).
  • Fixed InnoDB compilation warnings on CentOS 5. Bug fixed #962940 (Laurynas Biveinis).
  • Fixed MySQL upstream bug #64160 that was causing issues on upgrade to 5.5.20 and 5.5.21. Bug fixed #966844 (Stewart Smith).

Full release notes are available in the documentation.



  1. says


    Thank you for rolling out this release promptly. It is great to see you can make a new release promptly than there are critical customer affecting bugs to be fixed.

  2. AD says

    Yep, much appreciated – thanks!

    Btw, is Percona looking to create a build for the 5.6.x series? We are trying to decide between Percona 5.5.x vs Mysql 5.6.x (assuming that goes GA by summer) for a new project and would like to know your thinking.

    (FWIW – we have a support contract w/ Percona)


  3. says

    We’re keeping a close eye on MySQL 5.6.x, and there’s certainly things in Percona Server 5.5 that our customers would find valuable in a Percona Server based on MySQL 5.6. So, connecting the dots… there’s a good chance there’ll be one :)

    I wouldn’t be able to say the exact timetable for a GA Percona Server 5.6 after a MySQL 5.6… but we plan to have one sooner rather than later.

  4. Zach Bailey says

    Peter or Stewart,

    Any idea which upcoming version of Percona Server will incorporate this important bugfix:

    We’ve been waiting for this bug to be fixed for almost a year now so we can upgrade to 5.5. As Peter says, for us this is certainly one of those “critical customer affecting bugs” that we were hoping would be fixed quickly.


  5. says

    You can engage Percona to port the fix into 5.5, but at this stage it looks like we’ll get it following whatever 5.5 release Oracle puts the fix into.

Leave a Reply

Your email address will not be published. Required fields are marked *