Based on MySQL 5.5.51, including all the bug fixes in it, Percona Server 5.5.51-38.1 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.51-38.1 milestone at Launchpad.
DROP DATABASEwould fail to delete some of the tables in the database, the partially-executed command is logged in the binlog as
DROP TABLE t1, t2, ...for the tables for which drop succeeded. A slave might fail to replicate such
DROP TABLEstatement if there exist foreign key relationships to any of the dropped tables and the slave has a different schema from master. Fix by checking, on the master, whether any of the database to be dropped tables participate in a Foreign Key relationship, and fail the
DROP DATABASEstatement immediately. Bug fixed #1525407 (upstream #79610).
Percona Server 5.5 could not be built with the
-DMYSQL_MAINTAINER_MODE=ONoption. Bug fixed #1590454.
.gitignorein the percona-server source distribution had a line
*.spec, which means someone trying to check in a copy of the percona-server source would be missing the spec file required to build the RPMs. Bug fixed #1600051.
The fix for bug #1341067 added a call to free some of the heap memory allocated by OpenSSL. This is not safe for repeated calls if OpenSSL is linked twice through different libraries and each is trying to free the same. Bug fixed #1604676.
If the changed page bitmap redo log tracking thread stops due to any reason, then shutdown will wait for a long time for the log tracker thread to quit, which it never does. Bug fixed #1606821.
Performing slow InnoDB shutdown (
0) could result in incomplete purge, if a separate purge thread is running (which is a default in Percona Server). Bug fixed #1609364.
Other bugs fixed: #1515591 (upstream #79249), #1612551, #1609523, #756387, #1097870, #1603073, #1606478, #1606572, #1606782, #1607224, #1607359, #1607606, #1607607, #1607671, #1608385, #1608424, #1608437, #1608515, #1608845, #1609422, #1610858, #1612084, #1612118, and #1613641.
For general inquiries, please send us your question and someone will contact you.