MySQL增强版本Percona Server 5.6.17-65.0/5.5.37-35.0发布.2014-05-06.基于MySQL 5.6.17/5.5.37.落后于MariaDB了。有两个TokuDB增强，增加了审计日志插件，增加了Metrics for scalability measurement，支持Ubuntu 14.04及一些Bug修正。
Percona Server 5.6.17-65.0
Based on MySQL 5.6.17, including all the bug fixes in it, Percona Server 5.6.17-65.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-65.0 milestone at Launchpad.
Percona Server now supports Metrics for scalability measurement.
Percona Server now supports Audit Log Plugin.
Percona Server parser and query optimizer now support Multiple Clustering Keys when TokuDB engine is used.
Storage engine handler interface has been extended with new calls to notify the storage engine of imminent table or index scan. The calls are used by TokuDB to improve performance of these operations.
Percona Server packages are now available for Ubuntu 14.04.
Fixed the inadequate background LRU flushing for write workloads with InnoDB compression that could lead to lower performance. Bug fixed #1295268.
Percona Server debug packages were not built for the previous releases. Bug fixed #1298352.
Queries that no longer exceedlong_query_timewere written to the slow query log if they matched the previouslong_query_timevalue when slow_query_log_use_global_control variable was set toall. Bug fixed #1016991.
Previous implementation of the log_slow_rate_type set toquerywith log_slow_rate_limit feature would log every nth query deterministically instead of each query having a 1/n probability to get logged. Fixed by randomly selecting the queries to be logged instead of logging every nth query. Bug fixed #1287650.
Percona Server source files were referencing Maatkit instead of Percona Toolkit. Bug fixed #1174779.
Maximum allowed value for log_slow_rate_limit wasULONG_MAX(ie. either4294967295or18446744073709551615, depending on the platform). As it was unreasonable to configure the slow log for every four billionth session/query, new maximum allowed value is set to1000. Bug fixed #1290714.