Percona Server 5.6.22-71.0 發布

Percona Server 5.6.22-71.0 發布了，Percona 為 MySQL 數據庫服務器進行了改進，在功能和性能上較 MySQL 有著很顯著的提升。該版本提升了在高負載情況下的 InnoDB 的性能、為 DBA 提供一些非常有用的性能診斷工具；另外有更多的參數和命令來控制服務器行為。

Percona Server 只包含 MySQL 的服務器版，并沒有提供相應對 MySQL 的 Connector 和 GUI 工具進行改進。

該版本基于 MySQL 5.6.22，主要改進包括：

New Features:

• Percona Server has implemented improved slow log reporting for queries in stored procedures.

• TokuDB storage engine package has been updated to version 7.5.4. Percona Server with an older version of TokuDB could hit an early scaling limit when the binary log was enabled. TokuDB 7.5.4 fixes this problem by using the hints supplied by the binary log group commit algorithm to avoid fsync’ing its recovery log during the commit phase of the 2 phase commit algorithm that MySQL uses for transactions when the binary log is enabled.

Bugs Fixed:

• Debian and Ubuntu init scripts no longer have a hardcoded server startup timeout. This has been done to accommodate situations where server startup takes a very long time, for example, due to a crash recovery or buffer pool dump restore. Bugs fixed #1072538 and #1328262.

• A read-write workload on compressed InnoDB tables might have caused an assertion error. Bug fixed #1268656.

• Selecting from GLOBAL_TEMPORARY_TABLES table while running an onlineALTER TABLEin parallel could lead to server crash. Bug fixed #1294190.

• A wrong stack size calculation could lead to a server crash when Performance Schema tables were storing big amount of data or in case of server being under highly concurrent load. Bug fixed #1351148 (upstream #73979).

• A query on an empty table with aBLOBcolumn may crash the server. Bug fixed #1384568 (upstream #74644).

• A read-write workload on compressed InnoDB tables might have caused an assertion error. Bug fixed #1395543.

• If HandlerSocket was enabled, the server would hang during shutdown. Bug fixed #1397859.

• The default MySQL configuration file,my.cnf, was not installed during a new installation on CentOS. Bug fixed #1405667.

• The query optimizer did not pick a covering index for someORDER BYqueries. Bug fixed #1394967 (upstream #57430).

• SHOW ENGINE INNODB STATUSwas displaying two identicalTRANSACTIONSsections. Bug fixed #1404565.

• A race condition in Multiple user level locks per connection implementation could cause a deadlock. Bug fixed #1405076.

Other bugs fixed: #1394357, #1337251, #1399174, #1396330 (upstream #74987), and #1401776 (upstream #75189).