Based on MySQL 5.1.58, including all the bug fixes in it, Percona Server 5.1.58-12.9 is now the current stable release in the 5.1 series. All of Percona’s software is open-source and free, all the details of the release can be found in the 5.1.58-12.9 milestone at Launchpad.
fsync()has been replaced with
fdatasync()to improve perfomance where possible. The former is intended to sync the metadata of the file also (size, name, access time, etc.), but for the transaction log and the doublewrite buffer, such sync of metadata isn’t needed. Bug Fixed: #803270 (Yasufumi Kinoshita).
Two new collations,
ucs2_general50_ci, have been to improve compatibility for those upgrading from MySQL 5.0 or 5.1 prior to version 5.1.24.
A fix for a MySQL bug (#27877) introduced an incompatible change in collations in MySQL 5.1.24. If the following collations were used:
and any of the indexes contained the German letter “U+00DF SHARP S” ‘ß’ (which became equal to ‘s’), when upgrading from 5.0 / 5.1.23 or lower:
This problem is avoided when upgrading to Percona Server by converting the affected tables or columns to the collations introduced:
Blueprint:utf8-general50-ci-5.1 (Alexey Kopytov).
The ”SHM” buffer pool patch has been removed due to being both invasive and not widely used.
Instead, we recommend using the much safer LRU Dump/Restore patch, which provides similar improvements in restart performance and has the advantage of persisting across machine restarts.
The configuration variables for
my.cnf have been kept for compatibility and warnings will be printed for the deprecated options (
innodb_buffer_pool_shm_checksum) if used.
global_temporary_tablescaused the server to crash in some scenarios due to insufficient locking. Fixed by introducing a new mutex to protect from race conditions. Bugs Fixed:#745241 (Alexey Kopytov).
ignore-builtin-innodbis incompatible with Percona Server with XtraDB, the server will not start and print the corresponding error instead. Bug Fixed: #704216 (Laurynas Biveinis).
ALTER TABLEstatement leaded to a server crash. Bug Fixed: #627189 (Yasufumi Kinoshita).
innodb_lazy_drop_tableoption led to an assertion error when truncating a table in some scenarios. Bug Fixed:#798371 (Yasufumi Kinoshita).
For more information, please see the following links: