Percona Server for MySQL 5.6.38-83.0

Percona is glad to announce the release of Percona Server for MySQL 5.6.38-83.0 on December 8, 2017 (Downloads are available here and from the Percona Software Repositories).

Based on MySQL 5.6.38, including all the bug fixes in it, Percona Server for MySQL 5.6.38-83.0 is the current 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.38-83.0 milestone at Launchpad.

New Features

Percona Server for MySQL has implemented InnoDB Page Fragmentation Counters.

Percona Server for MySQL has implemented support for Multiple page asynchronous I/O requests. This feature was ported from a Facebook MySQL patch.

Percona Server for MySQL has implemented TokuDB integration with PERFORMANCE_SCHEMA.

Percona Server for MySQL packages are now available for Ubuntu 17.10 (Artful).

Bugs Fixed

Dynamic row format feature to support BLOB/VARCHAR in MEMORY tables requires all the key columns to come before any BLOB columns. This requirement however was not enforced, allowing creating MEMORY tables in unsupported column configurations, which then crashed or lose data in usage. Bug fixed #1731483.

If an I/O syscall returned an error during the server shutdown with Thread Pool enabled, a mutex could be left locked. Bug fixed #1702330 (Daniel Black).

After fixing bug #1668602, bug #1539504, and bug #1313901, CREATE/DROP TEMPORARY TABLE statements were forbidden incorrectly in transactional contexts, including function and trigger calls, even when they required no binary logging at all. Bug fixed #1711781.

Running ANALYZE TABLE while a long-running query is accessing the same table in parallel could lead to a situation where new queries on the same table are blocked in a Waiting for table flush state. Fixed by stopping ANALYZE TABLE flushing affected InnoDB and TokuDB tables from the table definition cache. Bug fixed #1704195 (upstream #87065).

MyRocks additions to the 5.6 mysqldump output have been removed.

CREATE TABLE ... LIKE ... did not use source row_format on target TokuDB table. Bug fixed #76.

TokuDB would encode already encoded database name for a directory name. Bug fixed #74.

Other bugs fixed: #1670902 (upstream #85352), #1670902 (upstream #85352), #1729241, #83, #80, and #75.