What's new in this version:
- The validate_password plugin now supports the capability of rejecting passwords that match the current session user name, either forward or in reverse. To enable control over this capability, the plugin exposes a validate_password_check_user_name system variable. By default, this variable is disabled; the default will change to enabled in MySQL 8.0. For more information, see Password Validation Plugin Options and Variables.
Test Suite Notes:
- In mysql-test-run.pl, a limit of 50 was imposed on the number of workers for parallel testing, which on systems with more than 50 CPUs resulted in exhaustion of unique thread IDs. The ID-exhaustion problem has been corrected, and the limit of 50 on number of workers has been lifted. Thanks to Daniel Black for the patch on which this change was based.
Functionality Added or Changed:
- InnoDB: A new dynamic configuration option, innodb_deadlock_detect, can be used to disable deadlock detection. On high concurrency systems, deadlock detection can cause a slowdown when numerous threads wait for the same lock. At times, it may be more efficient to disable deadlock detection and rely on the innodb_lock_wait_timeout setting for transaction rollback when a deadlock occurs.
- The systemd support script for the unit file (mysqld_pre_systemd) now assists in creating the error log file only if its location matches the pattern /var/log/mysql*.log. In other cases, the error log directory must be writable or the error log must be present and writable for the user running the mysqld process. Also, mysqld_pre_systemd now avoids creating insecure temporary files.
- The CMake WITH_LZ4 option has been added to control which LZ4 library is used during compilation. By default WITH_LZ4 is set to bundled, so the library provided with MySQL is used. Setting WITH_LZ4 to system uses the LZ4 library from the operating system.
- InnoDB: An ALTER TABLE ... ENCRYPTION='Y', ALGORITHM=COPY operation on a table residing in the system tablespace raised an assertion.
- InnoDB: Creating an encrypted table on a Fusion-io disk with an innodb_flush_method setting of O_DIRECT caused a fatal error.
- InnoDB: An operation that dropped and created a full-text search table raised an assertion.
- InnoDB: Accessing full-text search auxiliary tables while dropping the indexed table raised an assertion.
- InnoDB: An online DDL operation on a table with indexed BLOB columns raised an assertion during logging of table modifications.
- InnoDB: In some cases, code that locates a buffer pool chunk corresponding to given pointer returned the wrong chunk.
- Thanks to Alexey Kopytov for the patch.
- Replication: The addition of the transaction-write-set-extraction=XXH64 option uses xxHash symbols from liblz4. Although the xxHash symbols are exported by liblz4, the header file is not part of the API, so compilation failed when building with WITH_LZ4=system. The fix ensures that xxHash is built separately from liblz4 so that it is available both when using the system and bundled LZ4 libraries.
- Replication: mysqlbinlog --read-from-remote-server log1 log2 was opening a new connection for log2 without freeing the connection used for log1. Thanks to Laurynas Biveinis for the contribution.
- Replication: The MTR binary log test suite failed to clean up copied files. Thanks to Daniel Black for the contribution.
- Replication: With binlog_row_image=FULL, when updating single tables temporary tables were unnecessarily being used. The fix ensures single table update follows the same pattern as multi-table update.
- mysqld_safe attempted to read my.cnf in the data directory, although that is no longer a standard option file location.
- For mysqld_safe, the argument to --malloc-lib now must be one of the directories /usr/lib, /usr/lib64, /usr/lib/i386-linux-gnu, or /usr/lib/x86_64-linux-gnu. In addition, the --mysqld and --mysqld-version options can be used only on the command line and not in an option file.
- It was possible to write log files ending with .ini or .cnf that later could be parsed as option files. The general query log and slow query log can no longer be written to a file ending with .ini or .cnf.
- Privilege escalation was possible by exploiting the way REPAIR TABLE used temporary files.
- The client library failed to build on Solaris using the Cstd library.
- If the basedir system variable was set at server startup from the command line or option file, the value was not normalized (on Windows, / was not replaced with /).
- kevent statement timer subsystem deinitialization was revised to avoid a mysqld hang during shutdown on OS X 10.12.
- For accounts for which multiple GRANT statements applied, mysqlpump could fail to dump them all.
- The MYSQL_ADD_PLUGIN macro had a spelling error that caused MYSQL_SERVER not to be defined.
- In-place ALTER TABLE operations which when executed separately caused no table rebuild could when combined into a single statement result in a table rebuild.
- For keyring plugins, the data access layer is now created only as necessary, not once per operation, which improves keyring performance.
- A blank server name in CREATE SERVER statements produced a server exit rather than an error.
- The optimizer failed to check a function return value for an area calculation, leading to a server exit.
- The server could fail to free memory allocated for execution of queries that used generated columns.
- mysqlpump output for triggers that contained multiple statements in the trigger body failed to load correctly.
- Queries that satisfied the following conditions could return different results than in MySQL 5.6: 1) A subquery appeared in the select list; 2) The subquery contained a WHERE condition that referenced a value in the outer query; 3) The outer query contained a GROUP BY that required creation of a temporary table.
- Passwords that were rejected by the validate_password plugin were written by the server to the error log as cleartext.
- A prepared statement that used a parameter in the select list of a derived table that was part of a join could cause a server exit.
- MEDIUMINT columns used in operations with long integer values could result in buffer overflow.
- A spurious ER_NO_SUCH_TABLE error could occur when attempting to execute a prepared CREATE TABLE ... SELECT statement that used a temporary table in the FROM clause and called a stored function. The same error could occur for a nonprepared version of the statement if used in a stored procedure when the procedure was re-executed.
- EINTR handling in the client library has been fixed so that interrupted read and write calls are retried. Previously, EINTR was ignored.