EmergencyEMERGENCY? Get 24/7 Help Now!

Percona Server 5.5.17-22.1 released


Posted on:

|

By:


PREVIOUS POST
NEXT POST
Share Button

Percona is glad to announce the release of Percona Server 5.5.17-22.1 on November 19th, 2011 (Downloads are available here and from the Percona Software Repositories).

Based on MySQL 5.5.17, including all the bug fixes in it, Percona Server 5.5.17-22.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.17-22.1 milestone at Launchpad or in the Release Notes for 5.5.17-22.1 in the documentation.

Bug Fixes

  • MyISAM repair-by-sort buffer could not be greater than 4GB even on 64bit architectures. Bug Fixed: #878404 (Alexey Kopytov).
  • The kill idle transactions feature in XtraDB (if enabled) could sometimes cause the server to crash. Bug Fixed: #871722 (Yasufumi Kinoshita).
  • In a master-master setup when using SET user variables it was possible to have SHOW SLAVE STATUS give incorrect output due to a corrupted relay log. Bug Fixed: #860910 (Alexey Kopytov).
Share Button
PREVIOUS POST
NEXT POST


Stewart Smith

Stewart Smith has a deep background in database internals including MySQL, MySQL Cluster, Drizzle, InnoDB and HailDB. he is also one of the founding core developers of the Drizzle database server. He served at Percona from 2011-2014. He is a former Percona employee.



Categories:
Percona Software


Leave a Reply

Percona’s widely read Percona Data Performance blog highlights our expertise in enterprise-class software, support, consulting and managed services solutions for both MySQL® and MongoDB® across traditional and cloud-based platforms. The decades of experience represented by our consultants is found daily in numerous and relevant blog posts.

Besides specific database help, the blog also provides notices on upcoming events and webinars.

Want to get weekly updates listing the latest blog posts? Subscribe to our blog now! Submit your email address below.

No, thank you. Please do not ask me again.