Documentation Home
MySQL 5.5 Release Notes
Related Documentation Download these Release Notes
PDF (US Ltr) - 1.7Mb
PDF (A4) - 1.7Mb


MySQL 5.5 Release Notes  /  Changes in MySQL 5.5.51 (2016-07-29, General Availability)

Changes in MySQL 5.5.51 (2016-07-29, General Availability)

Bugs Fixed

  • Incompatible Change: For multibyte character sets, LOAD DATA could fail to allocate space correctly and ignore input rows as a result.

    A consequence of this change is that previously accepted invalid character data is now rejected, which can cause issues if you replicate from an older server without this bug fix to a newer server with this bug fix. For example, if an older server that accepts invalid utf8 character set data replicates to a newer server with this bug fix, the newer server will not accept the data and replication will fail with an Invalid utf8 character string error. Solutions for this issue include:

    • Correct the invalid data so that it is correct for the character set

    • Use a different character set for which the data is not invalid

    • Upgrade the master to a version that has the bug fix so that master and slave interpret the data the same way

    (Bug #76237, Bug #20683959, Bug #23080148)

    References: This issue is a regression of: Bug #14653594.

  • Replication: When using statement-based or mixed binary logging format with --read-only=ON, it was not possible to modify temporary tables. (Bug #62008, Bug #12818255)

    References: See also: Bug #14294223, Bug #16561483.

  • MySQL Server upgrades performed using RPM packages failed when upgrading from MySQL 5.1 Community to MySQL 5.5 Community or MySQL 5.1 Commercial to MySQL 5.5 Commercial. (Bug #23736787)

  • A buffer overflow in the regex library was fixed. (Bug #23498283)

  • Certain arguments to NAME_CONST() could cause a server exit. (Bug #23279858)

  • Installing MySQL from a yum or zypper repository resulted in /var/log/mysqld.log being created with incorrect user and group permissions. (Bug #21879694, Bug #78512)

  • If a stored function updated a view for which the view table had a trigger defined that updated another table, it could fail and report an error that an existing table did not exist. (Bug #21142859, Bug #76808)

  • If an INSTALL PLUGIN statement contained invalid UTF-8 characters in the shared library name, it caused the server to hang (or to raise an assertion in debug builds). (Bug #14653594, Bug #23080148)