Percona Server for MySQL 5.6.13-61.0¶
Percona is glad to announce the first GA (Generally Available) release of Percona Server for MySQL 5.6.13-61.0 on October 7th, 2013 (Downloads are available here and from the Percona Software Repositories.
Based on MySQL 5.6.13, including all the bug fixes in it, Percona Server for MySQL 5.6.13-61.0 is the first GA release in the Percona Server for MySQL 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.13-61.0 milestone at Launchpad.
Percona Server for MySQL has implemented a number of XtraDB performance improvements for I/O-bound high-concurrency workloads. This feature fixes the upstream bug: #68555 (#1236884).
Percona Server for MySQL has implemented a number of performance improvements for Page cleaner thread tuning. This feature fixes the upstream bugs: #69170 (#1231918), #70453 (#1232101) and #68481 (#1232406).
innodb_flush_methodhas been ported from Percona Server for MySQL 5.5.
Statement Timeout feature has been ported from the Twitter branch.
Percona Server for MySQL has extended the
SELECT INTO ... OUTFILEand
SELECT INTO DUMPFILEto add the support for UNIX sockets and named pipes.
Due to an incompatible upstream change that went in unnoticed, the log tracker thread would attempt to replay any file operations it encountered. In most cases this were a no-op, but there were race conditions for certain DDL operations that would have resulted in server crash. Bug fixed #1217002.
apt-get upgradeof Percona Server for MySQL would fail in post-installation step if server failed to start. Bug fixed #1002500.
Percona Server for MySQL 5.6 now ships with memcached plugins. Bug fixed #1159621.
libssl.so.6dependency issues in binary tarballs releases. Bug fixed #1172916.
install_layout.cmakecould cause that some library files, during the build, end up in different directories on x86_64 environment. Bug fixed #1174300.
A server could have crashed under a heavy I/O-bound workload involving compressed InnoDB tables. Bug fixed #1224432.