Percona Server 5.6.29-76.2 is now available

March 7, 2016

Author

Hrvoje Matijakovic

MySQL

Percona Events

Percona Software

Share this Post:

Percona is glad to announce the release of Percona Server 5.6.29-76.2 on March 7, 2016. Download the latest version from the Percona web site or from the Percona Software Repositories.

Based on MySQL 5.6.29, including all the bug fixes in it, Percona Server 5.6.29-76.2 is the current GA release in the Percona Server 5.6 series. Percona Server is open-source and free – this is the latest release of our enhanced, drop-in replacement for MySQL. Complete details of this release can be found in the 5.6.29-76.2 milestone on Launchpad.

Bugs Fixed:

With Expanded Fast Index Creation enabled, DDL queries involving InnoDB temporary tables would cause later queries on the same tables to produce warnings that their indexes were not found in the index translation table. Bug fixed #1233431.

Package upgrade on Ubuntu would run mysql_install_db even though data directory already existed. Bug fixed #1457614.

Package upgrade on Ubuntu and Debian could reset the GTID number sequence when post-install script was restarting the service. Bug fixed #1507812.

Starting MySQL with systemctl would fail with timeout if the socket was specified with a custom path. Bug fixed #1534825.

Write-heavy workload with a small buffer pool could lead to a deadlock when free buffers are exhausted. Bug fixed #1521905.

libjemalloc.so.1 was missing from binary tarball. Bug fixed #1537129.

mysqldumpslow script has been removed because it was not compatible with Percona Server extended slow query log format. Please use pt-query-digest from Percona Toolkit instead. Bug fixed #856910.

When cmake/make/make_binary_distribution workflow was used to produce binary tarballs it would produce tarballs with mysql-... naming instead of percona-server-.... Bug fixed #1540385.

Cardinality of partitioned TokuDB tables became inaccurate after the changes introduced by TokuDB Background ANALYZE TABLE feature in Percona Server 5.6.27-76.0. Bug fixed #925.

Running the TRUNCATE TABLE while TokuDB Background ANALYZE TABLE is enabled could lead to a server crash once analyze job tries to access the truncated table. Bug fixed #938.

Added proper memory cleanup if for some reason a TokuDB table is unable to be opened from a dead closed state. This prevents an assertion from happening the next time the table is attempted to be opened. Bug fixed #917.