EmergencyEMERGENCY? Get 24/7 Help Now!

Percona Server 5.6.17-66.0 is now available

 | June 11, 2014 |  Posted In: Events and Announcements, MySQL, Percona Server, Percona Software

PREVIOUS POST
NEXT POST

 

Percona ServerPercona is glad to announce the release of Percona Server 5.6.17-66.0 on June 11, 2014. Downloads are available here and from the Percona Software Repositories.

Based on MySQL 5.6.17, including all the bug fixes in it, Percona Server 5.6.17-66.0 is the current GA release in the Percona Server 5.6 series. All of Percona’s software is open-source and free, all the details of the release can be found in the 5.6.17-66.0 milestone at Launchpad.

 

New Features:

  • MySQL benchmarks (sql-bench directory in the MySQL distribution) has been made compatible with the TokuDB storage engine.
  • Percona Server has ported MariaDB code enhancement for start transaction with consistent snapshot. This enhancement makes binary log positions consistent with InnoDB transaction snapshots.
  • TokuDB Storage engine is now available as a separate package that can be installed along with the Percona Server 5.6.17-66.0. This feature is currently considered Release Candidate quality.
  • Percona Server has implemented ability to clone a snapshot created by START TRANSACTION WITH CONSISTENT SNAPSHOT in another session.
  • Percona Server 5.6 now includes HandlerSocket in addition to Percona Server 5.5.

Bugs Fixed:

  • Fix for #1225189 introduced a regression in Percona Server 5.6.13-61.0 which could lead to an error when running mysql_install_db. Bug fixed #1314596.
  • InnoDB could crash if workload contained writes to compressed tables. Bug fixed #1305364.
  • GUI clients such as MySQL Workbench could not authenticate with a user defined with auth_pam_compat plugin. Bug fixed #1166938.
  • Help in Percona Server 5.6 command line client was linking to Percona Server 5.1 manual. Bug fixed #1198775.
  • InnoDB redo log resizing could crash when XtraDB changed page tracking was enabled. Bug fixed #1204072.
  • Audit Log wasn’t parsing escape characters correctly in the OLD format. Bug fixed #1313696.
  • Percona Server version was reported incorrectly in Debian/Ubuntu packages. Bug fixed #1319670.

Other bugs fixed: #1318537 (upstream #72615), #1318874, #1285618, #1272732, #1314568, #1271178, and #1323014.

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

PREVIOUS POST
NEXT POST

2 Comments

  • Are there any plans to make the client library name configurable, so that those of us that need the client lib to be libmysqlclient instead of libperconaserverclient can handle it easily during the build process.

    Currently, I am forced to execute the following commands prior to compilation:

    find . -name CMakeLists.txt -exec sed -i -e ‘s;perconaserverclient;mysqlclient;g’ {} \;
    sed -i -e ‘s;perconaserverclient;mysqlclient;g’ libmysql/libmysql.{ver.in,map}

    It would be much easier to have a cmake parameter, such as -DWITH_LIBMYSQLCLIENT or something like that.

  • @Ken, thank you for the idea. I have logged this as an internal issue for consideration and possible implementation. Feel free to ping me on skype roel.mysql in a few weeks to see how it’s going (note to self; BLD-169).

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 and we’ll send you an update every Friday at 1pm ET.

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