Percona Server 5.1.69-14.7 now available: A drop in replacement for MySQL

Percona Server for MySQL version 5.1.69-14.7

Percona Server for MySQL version 5.1.69-14.7

Percona is glad to announce the release of Percona Server 5.1.69-14.7 on June 10, 2013. A drop in replacement for MySQL, downloads are available  here and from the Percona Software Repositories. Based on MySQL 5.1.69, this release will include all the bug fixes in it. All of Percona’s software is open-source and free, all the details of the release can be found in the 5.1.69-14.7 milestone at Launchpad.

Bugs Fixed:

  • In Ubuntu Precise libmysqlclient18 package was chosen from the distribution’s repository instead of Percona’s which could lead to package conflicts. Bug fixed #1174271.
  • Fixed the RPM Percona-Server-shared-compat package naming issue that could lead to unresolved package dependencies when installing Percona Server 5.1. Bug fixed #893860.
  • The log tracker thread was unaware of the situation when the oldest untracked log records are overwritten by the new log data. In some corner cases this could lead to assertion errors in the log parser or bad changed page data. Bug fixed #1108613.
  • Percona Server wouldn’t start if the XtraDB changed page tracking was enabled and variable innodb_flush_method was set to ALL_O_DIRECT. Bug fixed #1131949.
  • Fixed the RPM package dependencies for different major versions of Percona Server. Bug fixed #1167109.
  • Fixed the CVE-2012-5627 vulnerability, where an unprivileged MySQL account owner could perform brute-force password guessing attack on other accounts efficiently. This bug fix comes originally from MariaDB (see MDEV-3915). Bug fixed #1172090.
  • OpenSSL libraries were not found in 32-bit builds due to a typo. Bug fixed #1175447.
  • Query to the INNODB_CHANGED_PAGES table would cause server to stop with an I/O error if a bitmap file in the middle of requested LSN range was missing. Bug fixed #1179974.
  • Server would crash if an INNODB_CHANGED_PAGES query is issued that has an empty LSN range and thus does not need to read any bitmap files. Bug fixed #1184427.
  • Incorrect schema definition for the User Statistics tables in INFORMATION_SCHEMA (CLIENT_STATISTICS, INDEX_STATISTICS, TABLE_STATISTICS, THREAD_STATISTICS, and USER_STATISTICS) led to the maximum counter values being limited to 32-bit signed integers. Fixed so that these values can be 64-bit unsigned integers now. Bug fixed #714925.
  • mysql_set_permission was failing on Debian due to missing libdbd-mysql-perl package. Fixed by adding the package dependency. Bug fixed #1003776.
  • XtraDB changed page tracking used to hold the log system mutex for the log reads needlessly, potentially limiting performance on write-intensive workloads. Bug fixed #1171699.
  • Missing path separator between the directory and file name components in a bitmap file name could stop the server starting if the innodb_data_home_dir variable didn’t have the path separator at the end. Bug fixed #1181887.
  • A warning is now returned if a bitmap file I/O error occurs after an INNODB_CHANGED_PAGES query started returning data to indicate an incomplete result set. Bug fixed #1185040.
  • Fixed the upstream bug #69379 which caused MySQL clients to return bogus error number for host-not-found errors on Ubuntu 13.04. Bug fixed #1186690.
  • Under very rare circumstances, deleting a zero-size bitmap file at the right moment would make server stop with an I/O error if changed page tracking is enabled. Bug fixed #1184517.
  • The INNODB_CHANGED_PAGES table couldn’t be queried if the log tracker wasn’t running. Bug fixed #1185304.

Other bug fixes: bug fixed #1174346, bug fixed #1160951, bug fixed #1079688, bug fixed #1132412, bug fixed #1153651.

Release notes for Percona Server for MySQL 5.1.69-17.4 are available in our online documentation. Bugs can be reported on the launchpad bug tracker.

Share this post

Comments (4)

  • Moazam

    Hi Hrvoje,

    Few quick questions:

    1. I have a large innodb database, do I have to export databases from mysql and import them in Percona server or can I use mysql data directory?
    2. What’s the advantage of using Percona server over MySQL?
    3. I am using CentOS for my servers but i develop apps in windows, do you think percona will release windows version as well?


    June 10, 2013 at 6:29 pm
  • Hrvoje Matijakovic

    Hi Moazam,

    1) no, you don’t have to export databases, you can use the existing mysql data dir. But check if you’re planning to switch back from Percona Server

    2) here is the list of compared features:

    3) we’re not planning to release the windows versions of Percona Server at the moment

    June 11, 2013 at 1:18 am
  • Erez Zarum

    Why does the mysql client says it’s 5.1.70?
    Welcome to the MySQL monitor. Commands end with ; or g.
    Your MySQL connection id is 138
    Server version: 5.1.70-rel14.7-log Percona Server (GPL), 14.7, Revision 572

    June 17, 2013 at 5:58 am
  • Laurynas Biveinis

    Erez –

    In our 5.1.69-14.7 release we merged not the exact Oracle 5.1.69 sources, but a later version that is pre-5.1.70 due to Oracle putting a version tag on a wrong tree revision. They later created a new tag but we did not notice this. IMHO this is fairly benign even if inconvenient, we’ll resolve this by making a proper 5.1.70 release.

    June 20, 2013 at 5:07 am

Comments are closed.

Use Percona's Technical Forum to ask any follow-up questions on this blog topic.