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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>MySQL</strong> <strong>5.7</strong> <strong>Release</strong> <strong>Notes</strong>tried to transfer its exception condition to the diagnostics area of its caller that already contained acondition. (Bug #17400687)• In the Performance Schema memory instrumentation, statistics collected for memory-free operationscould be under-evaluated, leading to the appearance of a memory leak. (Bug #17400029)• KILL with an invalid thread ID value could raise an assertion. (Bug #17420682)• Compilation failures under Visual Studio 2012 were corrected. (Bug #17430236)• For JSON-format EXPLAIN statements, materialized views were incorrectly labeled asoptimized_away_subqueries rather than as materialized_from_subquery. (Bug#17428655)• In debug builds, SHOW PROCEDURE CODE raised an assertion. (Bug #17434385)• The mysql_real_connect() C API function could leak memory if it failed. (Bug #17337684)• Savepoints could not be used successfully following an ER_LOCK_DEADLOCK error (orER_LOCK_WAIT_TIMEOUT error, if innodb_rollback_on_timeout was enabled). (Bug#17356954)References: This bug is a regression of Bug #14188793.• The CLIENT_CONNECT_WITH_DB flag was improperly handled in the C client library. This could leadto a malformed packet sent to the server. (Bug #17351732)• Upgrades using RPM packages failed if the <strong>MySQL</strong> server was running due to failure to ignore themysqld_safe.pid file created by mysqld_safe. (Bug #17343851)• Compiling without the Performance Schema resulted in unresolved symbols. (Bug #17399658)• An assertion was raised if SET PASSWORD was used for an account that has been manually deletedfrom the mysql.user table but still present in memory. (Bug #17359329)• Some warnings produced by mysql_install_db referred to the now-deprecated log_warningssystem variable. These have been updated to refer to log_error_verbosity instead. (Bug#17363350)• Full-text search on InnoDB tables failed on searches that used the + boolean operator. (Bug#17280122)• The mysql_options() C API function could leak memory if called more than once with theMYSQL_SET_CLIENT_IP option. (Bug #17297012)• The CONV() function could call abs(INT_MIN), which is undefined, and cause a server exit. (Bug#17296644)• An error array in the SSL code was missing a comma, leading to implicit concatenation of adjacentmessages and a resulting off-by-one error in the relationship between error numbers and messages.(Bug #17294150)• Cost comparison for ref access could be inaccurate. (Bug #17303649)• The filesort implementation sometimes failed to allocate enough buffer space, leading to a serverexit. (Bug #17326567)• For single-threaded workloads, the optimizer recognizes some special cases for which it can avoidfunction calls and enhance performance. (Bug #17234723)• The my_load_path() function could in some cases calculate a path value incorrectly. (Bug#17204851)51

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

Saved successfully!

Ooh no, something went wrong!