Percona Server 5.5.46-37.5 is now available

November 5, 2015

Author

Hrvoje Matijakovic

MySQL

Percona Events

Percona Software

Share this Post:

Percona is glad to announce the release of Percona Server 5.5.46-37.5 on November 5, 2015. Based on MySQL 5.5.46, including all the bug fixes in it, Percona Server 5.5.46-37.5 is now the current stable release in the 5.5 series.

Percona Server is open-source and free. Details of the release can be found in the 5.5.46-37.5 milestone on Launchpad. Downloads are available here and from the Percona Software Repositories.

New Features:

Percona Server is now available for Ubuntu 15.10 (Wily).

Bugs Fixed:

Manipulating the innodb_track_redo_log_now variable dynamically would crash the server if it was started without innodb_track_changed_pages enabled. This variable is available on debug builds only. Bug fixed #1368530.

A potential crash in handling corrupted tables with innodb_corrupt_table_action warn or salvage values has been fixed. Bug fixed #1426610.

If the user had duplicate pid-file options in config files when running yum upgrade, the upgrade would stop with error because it would think it found the duplicate pid while it was the same pid specified twice. Bug fixed #1454917.

On some filesystems server would not start if XtraDB changed page tracking feature was enabled and innodb_flush_method variable was set to O_DIRECT. Bugs fixed #1500720 and #1498891.

When User Statistics are enabled, executing any statement of the SHOW family with non-empty result, would bump USER_STATISTICS ROWS_FETCHED column values erroneously. Bug fixed #1510953.

Fixed the conflicting meta packages between 5.1, 5.5, and 5.6 release series in Debian and Ubuntu distributions. percona-server-server and percona-server-client meta packages now point to the latest 5.6 release. Bug fixed #1292517.

INNODB_CHANGED_PAGES table was unavailable with non-default innodb_data_home_dir setting if the variable had a trailing slash. Bug fixed #1364315.

UPDATE statement could crash the server with Support for Fake Changes enabled. Bug fixed #1395706.

Changing innodb_fake_changes variable value in the middle of a transaction would have an immediate effect, that is, making part of the transaction run with fake changes enabled and the rest with fake changes disabled, resulting in a broken transaction. Fixed by making any innodb_fake_changes value changes becoming effective at the start of the next transaction instead of the next statement. Bug fixed #1395579.

Startup would fail due to a small hard-coded timeout value in the init script for the pid file to appear. This has been fixed by creating default file for Debian init script timeout parameters in etc/default/mysql. Bug fixed #1434022.