Percona is glad to announce the release of Percona Server 5.5.27-28.1 on September 5th, 2012 (Downloads are available here and from the Percona Software Repositories).

Based on MySQL 5.5.27, including all the bug fixes in it, Percona Server 5.5.27-28.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.27-28.1 milestone at Launchpad.

Bugs #1038225 and #1040735 are considered critical and we advise you to upgrade to this version if you’re using Percona Server 5.5.27-28.0.

Bugs Fixed:

  • Percona Server 5.5.27-28.0 would crash or deadlock in XtraDB buffer pool code. This was caused by incorrect mutex handling in porting of the recently introduced InnoDB code to XtraDB. Bug fixed #1038225 (Laurynas Biveinis).
  • Variables innodb_adaptive_flushing_method and innodb_flush_neighbor_pages would not correctly translate some values internally. Bug fixed #1039384 (Laurynas Biveinis).

Release notes for Percona Server 5.5.27-28.1 are available in our online documentation.

8 Comments
Oldest
Newest Most Voted
Inline Feedbacks
View all comments
Mark Leith

To be clear, Bug#1038225 was not a bug “caused by incorrect mutex handling in recently introduced InnoDB code.”, it was a bug in the merge process for XtraDB.

The mutex handling is fine in mainstream InnoDB, Percona missed that they should have updated it to use their own (not existing in mainstream MySQL/InnoDB) LRU_list_mutex, when merging upstream changes.

Mainstream MySQL does not have this bug.

0
Laurynas Biveinis

Mark, that is absolutely correct, we did not mean to imply any upstream bug here. I agree that the wording is very poor for that, we’ll adjust it.

0
Mark Leith

Thanks Laurynas, it looks a little better now. Could you also make sure that https://www.percona.com/doc/percona-server/5.5/release-notes/Percona-Server-5.5.27-28.1.html is updated consistently as well please?

0
Hrvoje Matijakovic

Mark, fix for release notes has already been submitted as well. It should be visible shortly.

0
Mark Leith

It seems the changelog still contains the old note…

0
Hrvoje Matijakovic

Mark, can you clarify what changelog you had in mind. Thank you.

0
Mark Leith

Oh, seems it was a browser caching issue! 🙂

/me shakes fist at browsers

Sorry.

0
Ben.

Thanks for the new release.

0