Percona Server 5.5.39-36.0¶

Percona is glad to announce the release of Percona Server 5.5.39-36.0 on August 29th, 2014. Downloads are available here and from the Percona Software Repositories.

Based on MySQL 5.5.39, including all the bug fixes in it, Percona Server 5.5.39-36.0 is now the current stable release in the 5.5 series. All of Percona‘s software is open-source and free, all the details of the release can be found in the 5.5.39-36.0 milestone at Launchpad.

New Features¶

Percona Server Audit Log Plugin now supports JSON and CSV formats. The format choice is controlled by audit_log_format variable.

Percona Server Audit Log Plugin now supports streaming the audit log to syslog.

Bugs Fixed¶

Querying INNODB_CHANGED_PAGES with a range condition START_LSN > x AND END_LSN < y would lead to a server crash if the range was empty with x greater than y. Bug fixed #1202252 (Jan Lindström and Sergei Petrunia).

With XtraDB changed page tracking feature enabled, queries from the INNODB_CHANGED_PAGES could read the bitmap data whose write was in still progress. This would cause the query to fail with an ER_CANT_FIND_SYSTEM_REC and a warning printed to the server error log. The workaround is to add an appropriate END_LSN-limiting condition to the query. Bug fixed #1346122.

mysqld-debug was missing from Debian packages. This regression was introduced in Percona Server 5.5.36-34.0. Bug fixed #1290087.

Fixed a memory leak in Slow Query Log Rotation and Expiration. Bug fixed #1314138.

The audit log plugin would write log with XML syntax errors when OLD and NEW formats were used. Bug fixed #1320879.

A server built with system OpenSSL support, such as the distributed Percona Server binaries, had SSL-related memory leaks. Bug fixed #1334743 (upstream #73126).

If the bitmap directory has a bitmap file sequence with a start LSN of one file less than a start LSN of the previous file, a debug build would assert when queries were run on INNODB_CHANGED_PAGES table. Bug fixed #1342494.

Server would crash on login attempt if mysql.user table was truncated. Bug fixed #1322218.