11.07.2015 Views

MySQL 5.7 Release Notes - Download - MySQL

MySQL 5.7 Release Notes - Download - MySQL

MySQL 5.7 Release Notes - Download - MySQL

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>MySQL</strong> <strong>5.7</strong> <strong>Release</strong> <strong>Notes</strong>• Some files in the Performance Schema file_instances table were not being removed becausethe file-removal operation was not instrumented. (Bug #69782, Bug #17209750)• mysqldump --single-transaction acquired metadata locks for each dumped table but did notrelease them until the dump operation finished. Consequently, other DDL operations on a dumpedtable blocked even after the table itself had been dumped. mysqldump now attempts to releasemetadata locks earlier. (Bug #71017, Bug #17862905)• Updating a FEDERATED table with UPDATE... JOIN caused a server exit when the local tablecontained a single row and that row could be joined to a row in the FEDERATED table. (Bug #68354,Bug #16324629)• The mysqladmin, mysqlbinlog, mysqlcheck, mysqldump, mysqlimport, mysqlslap, andmysqlshow programs now support a --secure-auth option that prevents sending passwords tothe server in old (pre-4.1) format. This option is enabled by default; use --skip-secure-auth todisable it. (Bug #69051, Bug #16723046)• During configuration, CMake improperly checked for the C++ header file cxxabi.h. (Bug #71268,Bug #18147458)• On Mac OS X, the libmysqlclient dylib file linked to itself. (Bug #61699, Bug #13890998, Bug#61243, Bug #12590037)• gcov printed warnings without file names. (Bug #33269, Bug #11747622)• cmake/configure.pl listed instances of WITH_COMMENT rather than the correct optionCOMPILATION_COMMENT. (Bug #65834, Bug #14298560)• FLUSH STATUS cleared a variable that could result a subsequent implicit commit of an XAtransaction causing a server exit. (Bug #70854, Bug #17911445)• A deadlock error occurring during subquery execution could cause an assertion to be raised. (Bug#69969, Bug #17307201)• The Performance Schema stage/sql/Waiting to get readlock instrument is no longer usedand has been removed. (Bug #71298, Bug #18035404)• A query that creates a temporary table to find distinct values and has a constant value in theprojected list could produce incorrect results. (Bug #70657, Bug #17634335)• mysqlbinlog leaked memory in relation to --rewrite-db processing. (Bug #71283, Bug#18027692)• Messages written by the server to the error log for LDML collation definition problems were missingthe collation name. (Bug #68144, Bug #16204175)• Configuring with -DWITH_DEBUG=1 did not have the same effect as configuring with -DCMAKE_BUILD_TYPE=Debug. (Bug #70647, Bug #17632854)• mysqlcheck did not correctly handle table names containing dots. (Bug #68015, Bug #16064833)• Previously, for EXPLAIN output, the rows-examined estimate for Performance Schema tables alwaysdisplayed as 1000. Now a more accurate estimate is displayed based on sizing parameters usedwhen allocating memory for each table. This results in no change of behavior because PerformanceSchema tables have no indexes. (Bug #71278, Bug #18024455)• Optimizer trace output from the range optimizer could include raw binary data and generateunprintable characters. Now binary data is printed in hex format. (Bug #71273, Bug #18023222)• The -DWITH_EXAMPLE_STORAGE_ENGINE=1 CMake option was ignored but should not have been.If -DWITH_EXAMPLE_STORAGE_ENGINE=0 is given, the EXAMPLE storage engine is built as aplugin. (Bug #70859, Bug #17772560)References: See also Bug #18324650.37

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!