Percona Server for MySQL 5.6.26-74.0¶
Based on MySQL 5.6.26, including all the bug fixes in it, Percona Server for MySQL 5.6.26-74.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.26-74.0 milestone at Launchpad.
TokuDB storage engine source has been merged into the Percona Server for MySQL code. TokuDB storage engine
tokudb_versionvariable now has the same value as the Percona Server for MySQL version variable
TokuDB Hot Backup has been renamed to Percona TokuBackup and it is now open source. Source code has been integrated into Percona Server for MySQL code as a git submodule. TokuDB Hot Backup plugin source has been merged into Percona Server for MySQL code.
Tokutek Fractal Tree has been renamed to Percona FT and its source code has been integrated into Percona Server for MySQL code as a git submodule.
TokuDB tests for Percona Server for MySQL 5.6 have been merged into Percona Server for MySQL 5.6 code.
Percona Server for MySQL has temporarily disabled savepoints in triggers and stored functions. The reason is that even having fixed bug #1438990 and bug #1464468 we have found more cases where savepoints in triggers break binary logging and replication, resulting in server crashes and broken slaves. This feature will be disabled until the above issues are properly resolved.
LOCK TABLES FOR BACKUPnow flushes the current binary log coordinates to InnoDB. Thus, under active
LOCK TABLES FOR BACKUP, the binary log coordinates in InnoDB are consistent with its redo log and any non-transactional updates (as the latter are blocked by
LOCK BINLOG FOR BACKUP). It is planned that this change will enable Percona XtraBackup to avoid issuing the more invasive
LOCK BINLOG FOR BACKUPcommand under some circumstances.
innodb_stresshas been added to the list of default MTR suites. For most supported systems satisfying the newly added dependencies is straightforward, but on CentOS 5, the default Python is too old. Thus
python26-mysqldbpackages should be installed there and
python26should be made the default python for the testsuite environment.
Percona Server for MySQL has implemented new
tokudb_enable_partial_evictionoption in TokuDB to allow disabling of partial eviction of nodes.
Percona Server for MySQL has implemented new
tokudb_compress_buffers_before_evictionoption in TokuDB which allows the evictor to compress unused internal node partitions in order to reduce memory requirements as a first step of partial eviction before fully evicting the partition and eventually the entire node.
libmylsqclient_16symbols were missing in Percona Server for MySQL shared library package on RHEL/CentOS 7. Bug fixed #1420691.
A sequence of failing
TRUNCATE TABLE, then insert to that table, and
CHECK TABLEwould crash the server. Bug fixed #1433197.
When InnoDB change buffering was enabled and used, executing a
FLUSH TABLE ... FOR EXPORTwould cause a server hang and
SHOW PROCESSLISTwould show that table in a
System Lockstate. Bug fixed #1454441 (upstream #77011).
RESET CHANGE_PAGE_BITMAPSpairs of commands were inadvertently joined, i.e. issuing either command had the effect of both. The first pair, besides flushing both index statistics and changed page bitmaps, had the effect of
RELOADprivilege. The second pair resulted in
FLUSH USER_STATISTICSdestroying changed page bitmaps. Bug fixed #1472251.
my.cnfwould result in server crashing on startup. The workaround is to enable
super_read_onlydynamically on a running server.Bug fixed #1389935 ( the fix was ported from Facebook patch #14d5d9).
If a new connection thread was created while a
SHOW PROCESSLISTcommand or a
INFORMATION_SCHEMA.PROCESSLISTquery was in progress, it could have a negative TIME_MS value returned in the PROCESSLIST output. Bug fixed #1379582.
LRU manager thread flushing was being accounted to
buffer_flush_backgroundInnoDB metrics which was wrong and redundant. Bug fixed #1491420.
Fixed a typo in the cleaner thread loop where
n_flushedis added to, instead of reset, by the idle server flushing. This may cause a cleaner thread sleep skip on a non-idle server. Bug fixed #1491435.
Running TokuDB for a long time with lots of file open and close operations could lead to a server crash due to server incorrectly setting a reserved value. Bug fixed #690.
Fixed TokuDB memory leak due to data race in context status initialization. Bug fixed #697.
Removed unnecessary calls to
malloc_usable_size()function in PerconaFT library to improve the performance. Bug fixed #682.