Documentation Home
MySQL 5.5 Release Notes
Related Documentation Download these Release Notes
PDF (US Ltr) - 1.2Mb
PDF (A4) - 1.2Mb
EPUB - 329.1Kb


MySQL 5.5 Release Notes  /  Changes in MySQL 5.5.42 (2015-02-02)

Changes in MySQL 5.5.42 (2015-02-02)

Functionality Added or Changed

  • SSL 2.0 and SSL 3.0 protocols are now explicitly disabled because they provide weak encryption. (Bug #19820550)

    References: See also: Bug #19921150.

  • yaSSL was upgraded to version 2.3.7. (Bug #19695101, Bug #20201864)

  • The valid date range of the SSL certificates in mysql-test/std_data has been extended to the year 2029. (Bug #18366947)

Bugs Fixed

  • InnoDB: An error occurred when the push_warning_printf function was invoked during server recovery. This function was previously used to print a warning message to the client. Also, current_thd was NULL when the server was restarted. (Bug #20144839)

  • InnoDB: A multiple-table delete operation caused the server to halt. (Bug #19815702)

  • Replication: If a DROP DATABASE statement failed on the master, mismatched tables could be left on the slave, breaking replication. This was caused by the DROP TABLE statement being binary logged if at least one table was deleted during the DROP DATABASE operation. The fix ensures that in such a situation the DROP TABLE statement is binary logged with the IF EXISTS option. (Bug #74890, Bug #20041860)

  • Unlocking a temporary table after locking and truncating it could cause a server exit. (Bug #19786309)

  • The Enterprise Encryption plugin could mishandle string arguments. (Bug #19688008, Bug #20730103)

  • FLUSH TABLES on a FEDERATED table failed if the table had been idle longer than the wait_timeout time plus the TCP keepalive time. (Bug #17599258)

  • Selecting all columns from INFORMATION_SCHEMA.TABLES did not reopen tables if they were in the table cache, but selecting a subset of those columns under the same conditions did reopen tables. (Bug #16869534)

  • MySQL failed to compile with GCC 4.9.1 in debug mode. (Bug #74710, Bug #19974500)

  • A file created for an internal temporary table could cause problems if the file was orphaned for some reason and the file name was reused for later queries. (Bug #32917, Bug #11747548)