Percona Server for MySQL 5.6.30-76.3¶
Based on MySQL 5.6.30, including all the bug fixes in it, Percona Server for MySQL 5.6.30-76.3 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.30-76.3 milestone at Launchpad.
When Read Free Replication was enabled for TokuDB and there was no explicit primary key for the replicated TokuDB table there could be duplicated records in the table on update operation. The fix disables Read Free Replication for tables without explicit primary key and does rows lookup for
DELETEbinary log events and issues warning. Bug fixed #1536663 (#950).
Percona Server for MySQL is now built with system
zliblibrary instead of the older bundled one. Bug fixed #1108016.
CREATE TABLE ... LIKE ...could create a system table with an unsupported enforced engine. Bug fixed #1540338.
Change buffer merge could throttle to 5% of I/O capacity on an idle server. Bug fixed #1547525.
Slave_open_temp_tableswould fail to decrement on the slave with disabled binary log if master was killed. Bug fixed #1567361.
Killed connection threads could get their sockets closed twice on shutdown. Bug fixed #1580227.
apt-cache showcommand for
innotopincluded as part of the package. Bug fixed #1201074.
Upgrade logic for figuring if TokuDB upgrade can be performed from the version on disk to the current version was broken due to regression introduced when fixing #684 in Percona Server for MySQL
5.6.27-75.0. Bug fixed #717.
ALTER TABLEwas run while
tokudb_auto_analyzevariable was enabled it would trigger auto-analysis, which could lead to a server crash if
ALTER TABLE DROP KEYwas used because it would be operating on the old table/key meta-data. Bug fixed #945.
The TokuDB storage engine with
1is safe to use in all conditions. On
REPLACE INTO, it tests to see if triggers exist on the table, or replication is active with
!BINLOG_FORMAT_STMTbefore it allows the optimization. If either of these conditions are met, then it falls back to the “safe” operation of looking up the target row first. Bug fixed #952.
Bug in TokuDB Index Condition Pushdown was causing
ORDER BY DESCto reverse the scan outside of the WHERE bounds. This would cause query to hang in a
sending datastate for several minutes in some environments with large amounts of data (3 billion records) if the
ORDER BY DESCstatement was used. Bugs fixed #988, #233, and #534.
Other bugs fixed: #1399562 (upstream #75112), #1510564 (upstream #78981), #1496282 (#964), #1496786 (#956), #1566790, #1552673, #1567247, #1567869, #718, #914, #970, #971, #972, #976, #977, #981, #637, and #982.