Security Notes

Functionality Added or Changed

Incompatible Change: For STANDALONE and WIN builds, the default secure_file_priv value has changed from the empty string to NULL. This is a secure-by-default setting because it disables import and export operations. To permit those operations, set secure_file_priv to the path name of the directory to use for those operations. (Bug #24679907, Bug #24695274, Bug #24707666)

The linked OpenSSL library for the MySQL Commercial Server has been updated to version 1.0.1u. For a description of issues fixed in this version, see http://www.openssl.org/news/vulnerabilities.html.

This change does not affect the Oracle-produced MySQL Community build of MySQL Server, which uses the yaSSL library instead. (Bug #24753389)

yaSSL was upgraded to version 2.4.2. This upgrade corrects issues with: Potential AES side channel leaks; DSA padding for unusual sizes; the SSL_CTX_load_verify_locations() OpenSSL compatibility function failing to handle long path directory names. (Bug #24512715, Bug #24740291)

Security Notes

Test Suite Notes

Functionality Added or Changed

Bugs Fixed

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.

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. Additionally, these changes were made:

(Bug #22342399, Bug #79585)

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. (Bug #23477773)

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. (Bug #24516262)

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. (Bug #23607230)

InnoDB: An ALTER TABLE ... ENCRYPTION='Y', ALGORITHM=COPY operation on a table residing in the system tablespace raised an assertion. (Bug #24381804)

InnoDB: Creating an encrypted table on a Fusion-io disk with an innodb_flush_method setting of O_DIRECT caused a fatal error. (Bug #24329079, Bug #82073)

InnoDB: An operation that dropped and created a full-text search table raised an assertion. (Bug #24315031)

InnoDB: Accessing full-text search auxiliary tables while dropping the indexed table raised an assertion. (Bug #24009272)

InnoDB: An online DDL operation on a table with indexed BLOB columns raised an assertion during logging of table modifications. (Bug #23760086)

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. (Bug #23631471, Bug #79378)

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. (Bug #82426, Bug #24399819)

References: See also: Bug #23607230.

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. (Bug #81675, Bug #23540182)

Replication: The MTR binary log test suite failed to clean up copied files. Thanks to Daniel Black for the contribution. (Bug #80881, Bug #23016254)

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. (Bug #79867, Bug #22510353)

mysqld_safe attempted to read my.cnf in the data directory, although that is no longer a standard option file location. (Bug #24482156)

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. (Bug #24464380)

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. (Bug #24388753)

Privilege escalation was possible by exploiting the way REPAIR TABLE used temporary files. (Bug #24388746)

The client library failed to build on Solaris using the Cstd library. (Bug #24353920)

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 \). (Bug #23747899, Bug #82125)

kevent statement timer subsystem deinitialization was revised to avoid a mysqld hang during shutdown on OS X 10.12. (Bug #23744004, Bug #82097)

For accounts for which multiple GRANT statements applied, mysqlpump could fail to dump them all. (Bug #23721446)

The MYSQL_ADD_PLUGIN macro had a spelling error that caused MYSQL_SERVER not to be defined. (Bug #23508762, Bug #81666)

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. (Bug #23475211, Bug #81587)

For keyring plugins, the data access layer is now created only as necessary, not once per operation, which improves keyring performance. (Bug #23337926)

A blank server name in CREATE SERVER statements produced a server exit rather than an error. (Bug #23295288)

The optimizer failed to check a function return value for an area calculation, leading to a server exit. (Bug #23280059)

The server could fail to free memory allocated for execution of queries that used generated columns. (Bug #23205454)

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

mysqlpump output for triggers that contained multiple statements in the trigger body failed to load correctly. (Bug #23072245)

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. (Bug #23049975)

Passwords that were rejected by the validate_password plugin were written by the server to the error log as cleartext. (Bug #22922023)

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. (Bug #22392374, Bug #24380263)

MEDIUMINT columns used in operations with long integer values could result in buffer overflow. (Bug #19984392)

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. (Bug #16672723, Bug #68972)

EINTR handling in the client library has been fixed so that interrupted read and write calls are retried. Previously, EINTR was ignored. (Bug #82019, Bug #23703570)

Performance Schema Notes

sys Schema Notes

Test Suite Notes

X Plugin Notes

Functionality Added or Changed

Bugs Fixed

The INFORMATION_SCHEMA INNODB_LOCKS and INNODB_LOCK_WAITS tables are now deprecated, to be removed in MySQL 8.0, which provides replacement Performance Schema tables.

The sys schema now has a quote_identifier() function that, given a string argument, produces a quoted identifier suitable for inclusion in SQL statements. (Bug #22011361, Bug #78823)

Output from the sys schema diagnostics() procedure now includes the Tls_version column from the mysql.slave_master_info system table.

mysql-test-run.pl now has a --manual-boot-gdb option that is similar to --boot-gdb but attaches the debugger to the server during the bootstrapping process, permitting the use of a remote debugger. (Bug #23090633)

When using SSL, only TLSv1 connections were being accepted. The fix ensures that all TLS versions supported by the server are accepted. (Bug #23524243)

Tests relating to X Plugin have been moved to rapid/plugin/x/test. (Bug #23151414)

Setting protocol related variables such as net_read_timeout, net_write_timeout, and net_retry_count, from a session using X Protocol returned unexpected results. The fix ensures that protocol variables are set only from sessions using MySQL Protocol, and errors are correctly detected for sessions using X Protocol.

The %global compatver value for RPM packages for RHEL/OEL and Fedora releases was updated from 5.6.25 to 5.6.31. (Bug #23038018)

References: See also: Bug #22980983.

Specifying an empty value for the --port option (for example, --port=, --port="") is now deprecated and results in a warning. An empty value will be an error in MySQL 8.0. (Bug #23023457, Bug #80903)

CMake support for compiling with Solaris Studio 12.5 was added. (Bug #82249, Bug #24303829, Bug #81274, Bug #23212938)

Performance: A flaw in the allocation of memory for appending string values caused some operations to be performed slowly, including creation of tables having generated columns and inserts of large values into JSON columns. (Bug #80556, Bug #22843444)

References: See also: Bug #22157531, Bug #22239803.

InnoDB: Full-text search auxiliary tables could be dropped by one session while being access by another. (Bug #23742339)

InnoDB: Selecting full-text index information schema tables for a deleted table caused a segmentation fault. (Bug #23479595)

InnoDB: A tablespace operation did not properly update the SYS_VIRTUAL system table. (Bug #23325659)

InnoDB: Rollback of a full-text index synchronization operation raised an assertion. The rollback operation attempted to acquire a mutex still held by the background synchronization thread. (Bug #23320569)

InnoDB: After compressing a table, an incorrect data length was passed to an internal tablespace encryption function, causing an assertion. (Bug #23279788)

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

InnoDB: An r-tree page lock placed during a search operation prevented an undo operation within the same transaction from merging pages. (Bug #23241575)

InnoDB: A bulk load insert of a record with a compressed size greater than half of the compressed page size resulted in infinite B-tree page splitting when compressing the uncompressed page. (Bug #23120933)

InnoDB: A lock order violation related to InnoDB full-text search caused errors and raised an assertion. (Bug #23120005)

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

InnoDB: In read-only mode, InnoDB attempted to set a corrupt bit in the SYS_INDEXES system table. In read-only mode, the corruption should only be marked in memory. (Bug #23077748)

InnoDB: InnoDB attempted to materialize non-key generated virtual columns that were not required for partitioning. (Bug #23037025)

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

InnoDB: An insert operation on a table containing virtual and spatial indexes raised an assertion due to an invalid parent path encountered during page splitting. (Bug #23008863)

InnoDB: An ALTER TABLE operation on a table with an indexed virtual column raised an assertion. (Bug #22965271)

InnoDB: Adding or dropping a generated virtual column could raise an assertion due to a table handle held by an active memcached connection. (Bug #22922527)

InnoDB: A full-text query that involved a large number of records exceeded the result cache limit and caused a server exit. (Bug #22709692, Bug #80296)

InnoDB: InnoDB did not block the creation of a foreign key constraint with referential actions on the base column of a generated stored column. (Bug #22687023, Bug #80304)

InnoDB: The optimizer failed to mark the columns required for MATCH function evaluation when the secondary index used for the full-text query was not chosen by the optimizer. (Bug #22679209, Bug #80298)

InnoDB: In READ COMMITTED isolation level, InnoDB unnecessarily acquired the lock_sys mutex at COMMIT for a transaction block consisting of read-only SELECT statements.

Thanks to Zhai Weixiang for the patch. (Bug #22617328, Bug #76728)

InnoDB: Setting innodb_monitor_enable to all did not enable all counters. (Bug #22576241, Bug #80083)

InnoDB: InnoDB now permits defining a foreign key constraint with a cascading referential action on the base column of an indexed virtual column, and defining cascading referential actions on non-virtual foreign key columns that are explicitly included in a virtual index. (Bug #22469130, Bug #79772)

InnoDB: An assertion was raised during rollback of an ALTER TABLE operation that dropped and added a secondary index. (Bug #22005726)

Partitioning: In some cases, an issue with partition pruning being attempted a second time during optimization after all partitions had already been pruned at parsing time led to an assert. (Bug #23194259)

Replication: A lack of cleanup in binlog.binlog_index led to sporadic failures in the i_binlog.binlog_index_crlf_check test. (Bug #23645554)

Replication: Replication slaves could exit trying to apply an UPDATE row event containing virtual generated columns received from a master that was set to binlog_row_image=minimal. (Bug #23604483)

Replication: The initialize process now checks if the binary log is enabled while processing a compiled statement. In such cases it disables binary logging. (Bug #23490641)

Replication: After upgrading from MySQL 5.6, MySQL 5.7 slaves were not handling replication channels correctly. This was due to the upgrade procedure inverting the order of two fields of the mysql.slave_master_info table (Channel_Name and Tls_version). The fix avoids this inversion and adds a check to ensure that the Channel_name is correctly used as the primary key. (Bug #23180202)

Replication: The i_rpl.rpl_relay_log_index_inconsistency test was not preserving the slave server state in certain situations. The fix changes the test to use start_slave.inc instead. (Bug #22850741)

Replication: When dealing with large GTID sets (bigger than 64 kilobytes when converted to a string), the replication_connection_status field was truncating the RECEIVED_TRANSACTION_SET. The fix updates replication_connection_status to correctly display large GTID sets, and also updates various GTID set related functions to avoid any future problems with large GTID sets. (Bug #22369630)

Replication: On a GTID-based replication slave running with --gtid-mode=on, --log-bin=OFF and using --slave-skip-errors, when an error was encountered that should be ignored Exec_Master_Log_Pos was not being correctly updated, causing Exec_Master_Log_Pos to loose synchrony with Read_master_log_pos. If a GTID_NEXT was not specified, the slave would never update its GTID state when rolling back from a single statement transaction. The Exec_Master_Log_Pos would not be updated because even though the transaction was finished, its GTID state would show otherwise. The fix removes the restraint of updating the GTID state when a transaction is rolled back only if GTID_NEXT is specified. (Bug #22268777)

Replication: Uncleared information related to user-defined variables could result in a server exit for DROP TEMPORARY TABLE statements. (Bug #22157118)

Replication: A server initialized with --gtid-mode=on and --enforce-gtid-consistency=on created a large and unnecessary GTID set. The fix adjusts the initialization process to eliminate the creation of these GTID sets. (Bug #22102456, Bug #78972)

Replication: An incorrectly formed server_uuid read in from auto.conf could cause an unexpected halt. (Bug #21936933)

Replication: After issuing a PURGE BINARY LOGS statement, if the binary log index file was not available, for example because it had been opened by another application such as MEB, the server could stop unexpectedly. Although this situation was rare, the handling has been made more robust to avoid unexpected halts and more informative errors are provided. (Bug #20381055)

Replication: The constructor of Rows_event has been improved to not decode the supplied row event one byte at a time. Thanks to Davi Arnaut for the contribution. (Bug #82003, Bug #23699294)

Replication: A new function has been added to the channel service interface to get a channel's retrieved_gtid_set. (Bug #81694, Bug #23519893)

Replication: Slaves running MySQL version 5.7.11 and later were always using SSL/TLS when the server supported it, regardless of the MASTER_SSL option. This was due to the addition of the --ssl-mode option, which defaults to preferring an SSL connection. The fix ensures that slaves do not use SSL when MASTER_SSL=0. (Bug #81223, Bug #23197529)

Replication: The mysql-test-run.pl option --skip-rpl now correctly skips all replication tests.

Thanks to Daniel Black for the contribution. (Bug #80894, Bug #23021140)

Replication: When --gtid-mode=off, issuing a PURGE BINARY LOGS TO file statement causes the system to read the whole file. Depending on the size of the file this could cause the server to stall for a few seconds. This was due to the way binary log files were being searched for the Previous_gtids value. The fix adds an optimization to stop the reading of the binary log file if it is supposed only to read the lost GTIDs and a Previous_gtids event is found. (Bug #80889, Bug #23054591)

Replication: When using row-based replication and InnoDB, replication slaves reverted to using an older locking scheme when a transaction had already acquired an AUTOINC lock related to a LOAD FILE or INSERT ... SELECT type of statement, reducing replication slave performance. The fix ensures that sql_command is set correctly for any of the DML events such as WRITE_ROWS_EVENT, UPDATE_EVENT, and DELETE_EVENT. (Bug #79324, Bug #22247668)

Replication: A MySQL version 5.5 slave does not have a server_uuid and replication identified servers by their server_id. Starting from MySQL version 5.6, replication masters detected a zombie dump thread based only on a slave's server_uuid value, under the assumption that each slave has a unique UUID. Connecting a MySQL 5.5 slave to a MySQL 5.6 and later master meant that the master was unable to detect zombie dump threads that were created to serve slaves running versions older than MySQL 5.6. The fix ensures that a master now first checks if a slave has a server_uuid set. If it is set, zombie dump thread detection happens based on the slave's UUID. If a slave's server_uuid is not set, zombie dump thread detection happens based on server_id. (Bug #77195, Bug #21179199)

Replication: With slave_skip_errors enabled there were still special cases when slave errors were not being correctly ignored. For example:

In these cases the error was considered critical and it was not respecting the state of slave_skip_errors. The fix ensures that with slave_skip_errors enabled, all errors reported during applying a transaction are correctly handled. This means that in such a set up, upon receiving an error with the log_warnings option set to greater than 1, if the error can be ignored then the warning is printed into the error log and the server continues as it does in the case of other ignored errors. (Bug #70640, Bug #17653275)

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.6 Community to MySQL 5.7 Community or MySQL 5.6 Commercial to MySQL 5.7 Commercial. (Bug #23736787)

On CentOS, mysqld installed from a MySQL Community distribution failed to start if a my.cnf file with no datadir value specified was used. (Bug #23721277, Bug #82049)

The -DWITH_EDITLINE=system CMake option failed with recent versions of the editline library. (Bug #23708332)

Executing prepared statements with the audit_log plugin installed could cause a server exit. (Bug #23699991)

The sys schema ps_trace_statement_digest() procedure failed for statements not supported by EXPLAIN, for statements for which EXPLAIN could not find tables, and for statements with no digest found during the monitored period. (Bug #23621189)

On RPM-based systems, it is now easier to install multiple client library versions, such as for the case that you want to maintain compatibility with older applications linked against previous libraries. To install an older client library, use the --oldpackage option with rpm. For example, to install mysql-community-libs-5.5 on an EL6 system that has libmysqlclient.20 from MySQL 5.7, use a command like this:

rpm --oldpackage -ivh mysql-community-libs-5.5.50-2.el6.x86_64.rpm

(Bug #23605713, Bug #81384)

A SELECT Performance Schema tables when an internal buffer was full could cause a server exit. (Bug #23550835, Bug #23298025, Bug #81464)

The code for reading character set information from Performance Schema statement events tables (for example, events_statements_current) did not prevent simultaneous writing to that information. As a result, the SQL query text character set could be invalid, which could result in a server exit. Now an invalid character set causes SQL_TEXT column truncation. (Bug #23540008)

An error message spelling error was corrected. Thanks to Derek Jones for the patch. (Bug #23525874, Bug #81713)

In the Performance Schema, allocating a record when a buffer was full could lead to a server exit. (Bug #23515302)

Several issues for Debian/Ubuntu packages were fixed:

(Bug #23501369, Bug #81647, Bug #22972977, Bug #21236550, Bug #21228746, Bug #22833016, Bug #23582336)

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

Upgrading from native MySQL 5.6 Debian/Ubuntu packages to Oracle-supplied MySQL 5.7 packages caused server restart failures. (Bug #23498230)

The CMake configuration was too aggressive in making symbols invisible, resulting in link problems with GCC 5.3 on Solaris. (Bug #23344916, Bug #81593)

Audit log filtering against the user was performing comparisons against USER(), not CURRENT_USER(). (Bug #23344762, Bug #81591)

After upgrading only the server using RPM packages, the server could fail to start, complaining about a bad errmsg.sys file. (Bug #23338603)

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

Several issues were addressed in the sys schema stored procedures that show enabled or disabled Performance Schema setup:

(Bug #23335880, Bug #81564, Bug #22066096, Bug #78874)

Upgrading from native Ubuntu 5.7.12 packages to MySQL 5.7.13 packages failed with conflict messages. (Bug #23327563)

For debug builds, the server exited abnormally if a shutdown command was issued while the audit_log plugin was loaded and an active connection existed. (Bug #23310864)

The server could fail to interpret expired passwords as expired. (Bug #23291841)

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

For unit-testing with the MySQL test suite, the make unit-test command is no longer available. The ctest program should be used instead. See Unit Tests Added to Main Test Runs. (Bug #23273434, Bug #81389)

Audit log plugins (including query rewrite plugins, which use the audit API) were being acquired and released per statement, negatively affecting scalability. To improve performance, these plugins now are acquired once and released only when the connection ends. (Bug #23236404, Bug #81298)

The -fexpensive-optimizations option to GCC caused ARM64 and PowerPC builds to compute floating-point operations slightly differently from other platforms. CMake now checks for this problem and disables the option as necessary. (Bug #23046775)

The test_service_sql_api.test_session_general_log test case now cleans up the general_log table by truncating it at the end of the test. Thanks to Daniel Black for the patch. (Bug #23021111, Bug #80895)

Lines written to the error log had no space separating the timestamp and thread ID columns if the thread ID took five or more characters. (Bug #23005009, Bug #80854)

For the innodb_buffer_stats_by_schema and innodb_buffer_stats_by_table sys schema views, the pages_hashed and pages_old columns were incorrect. Thanks to Tsubasa Tanaka for the patch. (Bug #22988461, Bug #80833)

An incorrect result could be returned for a query using a merged derived table or a view when compared to a similar query using a base table directly, if the query included a WHERE condition in a scalar subquery inside a HAVING condition of the main query block. (Bug #22967439)

ST_GeomFromGeoJSON() treated JSON NULL as invalid input. Now it treats JSON NULL as SQL NULL and thus returns SQL NULL for JSON NULL input. (Bug #22930020, Bug #80712)

For the host_summary_by_statement_latency and x$host_summary_by_statement_latency sys schema views, the max_latency column was incorrect. (Bug #22848110, Bug #80569)

ST_Distance() could raise an assertion for NULL return values. (Bug #22760390)

In the absence of SQL_CALC_FOUND_ROWS, FOUND_ROWS() for a UNION statement always returned the actual number of rows found even when LIMIT was present. (Bug #22602381, Bug #80148)

A statement containing a format specifier resulted in a server exit when the query rewrite plugin tried to log the statement. (Bug #22601485)

With the query cache enabled, executing a prepared statement with CURSOR_TYPE_READ_ONLY and then again with CURSOR_TYPE_NO_CURSOR caused the server to return an error. (Bug #22559575, Bug #80026)

mysql_real_connect() was not thread-safe when invoked with the MYSQL_READ_DEFAULT_FILE or MYSQL_READ_DEFAULT_GROUP option enabled. (Bug #22322504, Bug #79510)

With GTIDs enabled, XA COMMIT on a disconnected XA transaction within a multiple-statement transaction raised an assertion. (Bug #22173903)

The sys schema create_synonym_db() function failed if the synonym name was a reserved word or contained backtick (`) characters. (Bug #22011361, Bug #78823)

The sys schema host_summary view could fail with a division-by-zero error. (Bug #21970078)

The GCC workaround for compiling on ARM64 added by Bug #21552524 is needed only for GCC before 5.2.1. (Bug #21845828)

References: See also: Bug #21552524.

The sys schema format_path() function replaced substrings of the path name argument without verifying that the substrings were delimited by path name separators. Replacement now works correctly, including on Windows. A consequence is that backslashes in Windows path names are no longer converted to forward slashes in the result. (Bug #21512106)

MySQL now supports compiling using the GCC __atomic builtins introduced in GCC 4.7 that permit a more efficient implementation of the MySQL atomics API. These __atomic builtins are only used for platforms where the old GCC __sync builtins are not available, such as PowerPC where the server otherwise would not build. (Bug #21221500)

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)

mysql_upgrade failed to upgrade the sys schema if a sys database directory existed but was empty. (Bug #81352, Bug #23249846, Bug #22875519)

The bundled Protobuf sources (under the extra directory) were upgraded from version 2.6.0 to 2.6.1. (Bug #81280, Bug #23213376)

Protobuf is currently used only by the X Plugin, but MySQL builds built the protobuf libraries and executables even if X Plugin building was disabled with -DWITH_RAPID=0. (Bug #81066, Bug #23097750)

On Solaris, a misaligned memory buffer could cause a server exit when selecting from the global_status Performance Schema table. (Bug #81065, Bug #23097305)

A compilation error was corrected for a make_link() call when compiling in C++11 mode. Thanks for Daniel Black for the contribution. (Bug #80996, Bug #23080289)

Two mysql-test-run.pl tests (ctype_gb18030_binlog and ctype_ldml) failed to produce repeatable output due to improper cleanup. Thanks to Daniel Black for the patch. (Bug #80896, Bug #23021095)

MySQL failed to build with GCC 6 using the default mode for C++ of -std=gnu++14. The CMake configuration has been adjusted to explicitly set the mode to -std=gnu++03 for GCC 6. (Bug #80371, Bug #22732697)

Ubuntu packages create the root user account using the auth_socket authentication plugin to achieve secure-by-default installation if installation was done with a blank root password. However, auth_socket was being used even if the password was not blank. (Bug #80137, Bug #22594846, Bug #23321113, Bug #81518)

Compiling the InnoDB memcached plugin did not work on some platforms where MySQL was configured using -DWITH_LIBEVENT=system. (Bug #80073, Bug #22573379, Bug #23567441)

The client-side plugin deinitialization function signature was changed from int (*deinit)() to int (*deinit)(void) to avoid warnings when compiling with -Wstrict-prototypes. (Bug #78177, Bug #21680094, Bug #81419, Bug #23282498)

Account Management Notes

Audit Log Notes

Configuration Notes

Packaging Notes

Security Notes

X Plugin Notes

Functionality Added or Changed

Bugs Fixed

In MySQL 5.7.8, the maximum length of MySQL user names was increased from 16 to 32 characters, but some applicable contexts for this increase were overlooked. Additional changes in maximum user name length now have been applied:

If you upgrade to this MySQL release from an earlier version, you must run mysql_upgrade (and restart the server) to incorporate the changes to the mysql system database. A server from MySQL 5.7.13 or higher for which mysql_upgrade has not been run continues to permit a maximum of 77 characters in the system tables mentioned previously, and an ER_USER_COLUMN_OLD_LENGTH error will occur in those system table contexts where a user_name@host_name value from 78 to 93 characters long is given.

The audit_log plugin that forms the basis for MySQL Enterprise Audit now supports fine-grained filtering of events. This enables a reduction in the number of log entries written to the audit log file, which increases overall performance due to fewer write operations during log recording. It also simplifies subsequent audit log processing in terms of readability and processing time.

Fine-grained audit log filtering is rule based, implemented using tables that store filter definitions and a set of user-defined functions (UDFs) that enable filter manipulation. To simplify installing the tables and UDFs along with the audit_log plugin, an installation script is now provided. For more information, see Installing or Uninstalling MySQL Enterprise Audit, and Audit Log Filtering.

By default, audit log filtering now logs no auditable events for any users. This differs from legacy audit log behavior (before MySQL 5.7.13), which logs all auditable events for all users; to produce log-everything behavior, see the installation instructions.

References: See also: Bug #21464781, Bug #71855.

On platforms for which systemd support is installed, systemd has the capability of managing multiple MySQL instances. For details, see Configuring Multiple MySQL Instances Using systemd. Consequently, mysqld_multi and mysqld_multi.server are not installed because they are unnecessary. (Bug #81093, Bug #23134620)

support-files/MacOSX/ReadMe.txt is no longer included in MySQL distributions. (Bug #81038, Bug #23088916)

The linked OpenSSL library for the MySQL Commercial Server has been updated to version 1.0.1t. For a description of issues fixed in this version, see http://www.openssl.org/news/vulnerabilities.html.

This change does not affect the Oracle-produced MySQL Community build of MySQL Server, which uses the yaSSL library instead. (Bug #23229564)

MySQL Server now includes an SQL interface for keyring key management, implemented as a set of user-defined functions (UDFs) that access the functions provided by the internal keyring service. For more information, see Keyring Key Management Functions. For information about the keyring service functions invoked by the UDFs, see The Keyring Service. For general keyring information, see The MySQL Keyring.

The minimum number of X Plugin worker threads dropped below the number of threads configured by mysqlx_min_worker_threads. (Bug #23074173)

During installation of X Plugin, the DROP USER statement of an internal user was being added to the binary log, while the matching CREATE USER statement was not. This was causing an error in replication as the internal user did not exist on slaves. The fix ensures that the DROP USER statement is not added to the binary log. (Bug #22989849)

An error occurred when using method chaining to group results, for example Crud.Find({ name:$.name, count:count(*) }).GroupBy($.name);. (Bug #22950240)

X Plugin threads were registered in the P_S tables as thread/sql/daemon_plugin. This has been changed to thread/mysqlx/worker. (Bug #22901644)

When a Mysqlx_idle_worker_thread_timeout was configured, once the timeout had completed worker threads consumed 100% of CPU when they should have been idle. (Bug #81236, Bug #23204368)

Client disconnections were logged as EOF. The log message has been improved to Peer disconnection. (Bug #81199, Bug #23178878)

For better separation of output from multiple statements, mysqltest now flushes output sent to stdout when the output destination is not a file. Previously, flushing occurred only for file output. (Bug #21435906)

The version of the tcmalloc library included in MySQL distributions was very old. It has been removed and is no longer included with MySQL. (Bug #80994, Bug #23068660)

The my_make_scrambled_password() function in the C client library was restricted earlier in MySQL 5.7 (not exported to client programs). The function has once again been made visible to client programs. (Bug #80974, Bug #23061746)

It is possible to use ALTER TABLE to change the default value of a column col_name, which may change the value of a generated column expression that refers to the column using DEFAULT(col_name). For this reason, ALTER TABLE operations that change the definition of a column now cause a table rebuild if any generated column expression uses DEFAULT(). (Bug #80299, Bug #22680839)

This release adds an unquoting extraction operator ->>, sometimes also referred to as an inline path operator, for use with JSON documents stored in MySQL. The new operator is similar to the -> operator, but performs JSON unquoting of the value as well. For a JSON column mycol and JSON path expression mypath, the following three expressions are equivalent:

The ->> operator can be used in SQL statements wherever JSON_UNQUOTE(JSON_EXTRACT()) would be allowed. This includes (but is not limited to) SELECT lists, WHERE and HAVING clauses, and ORDER BY and GROUP BY clauses.

For more information, see Functions That Search JSON Values, and JSON Path Syntax. (Bug #78736, Bug #21980346)

InnoDB: A rollback operation run concurrently with an operation involving a generated virtual column caused a server exit. (Bug #23313102)

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

InnoDB: Potential buffer overflow issues were corrected for the InnoDB memcached plugin. (Bug #23187607)

InnoDB: An ALTER TABLE operation that added an AUTO_INCREMENT column on a table with virtual columns raised an assertion. (Bug #23052231)

InnoDB: Statements executed in a transaction that was rolled back asynchronously by a higher priority transaction caused a deadlock error and subsequent replication failure. (Bug #23021168, Bug #80898)

InnoDB: An ALTER TABLE operation that attempted to add a generated virtual column and a full-text index raised an assertion. (Bug #23014521)

InnoDB: The full-text index cache was freed during a background index cache synchronization. (Bug #22996488)

InnoDB: A full-text index operation raised an assertion. (Bug #22963169)

InnoDB: Memory was allocated to I/O slots unnecessarily, causing an apparent memory leak. (Bug #22956469, Bug #80772)

InnoDB: An ALTER TABLE operation raised an assertion when attempting to create a key containing a generated column. (Bug #22951879)

InnoDB: A startup failure due to an invalid option resulted in a server exit after a subsequent restart. An error returned by the innobase_start_or_create_for_mysql function was not checked. (Bug #22939581, Bug #80761)

InnoDB: An ALTER TABLE ... IMPORT TABLESPACE operation on file-per-table tablespace containing an encrypted table failed when run in a different session than the preceding ALTER TABLE ... DISCARD TABLESPACE operation. (Bug #22918999, Bug #80708)

InnoDB: A FLUSH TABLES operation on a table with a discarded tablespace raised an assertion. (Bug #22899690, Bug #80669)

InnoDB: A DML operation involving a table with a virtual column raised an assertion. (Bug #22899305)

InnoDB: An invalid read at innobase_get_computed_value() raised a Valgrind error. (Bug #22898168, Bug #80667)

InnoDB: Online DDL operations like ALTER TABLE ... ADD INDEX were not permitted for tables created with the ENCRYPTION attribute. (Bug #22897921)

InnoDB: InnoDB memcached code assumed the nonexistence of the htonll() function on OS X, resulting in a build failure on OS X 10.10 and later. (Bug #22865112)

InnoDB: Starting the server in read-only mode failed when encrypted tables were present. The call to fil_encryption_rotate() was not skipped when the server was started in read-only mode. (Bug #22723797)

InnoDB: An R-tree purge operation raised an assertion. (Bug #22698076, Bug #80327)

InnoDB: An INSERT operation on a table with a FULLTEXT index and FTS_DOC_ID column failed because the inserted FTS_DOC_ID value exceeded the permitted gap between consecutive FTS_DOC_ID values. To avoid this problem, the permitted gap between the largest used FTS_DOC_ID value and new FTS_DOC_ID value was raised from 10000 to 65535. (Bug #22679185)

InnoDB: Validation code for transparent page compression incorrectly permitted innodb_strict_mode=OFF, which allowed the COMPRESSION attribute to be applied to a general tablespace. Page compression is only supported with file-per-table tablespaces. (Bug #22615096, Bug #80182)

InnoDB: An memory order issue related to atomic operations caused assertion failures on ARM64 and POWER platforms. (Bug #22608616)

InnoDB: DROP TABLESPACE returned an error if the remote general tablespace data file was missing. (Bug #22232892, Bug #79330)

InnoDB: An ALTER TABLE operation that changed table row format from COMPACT to COMPRESSED raised an assertion. A function involved in the operation passed incorrect page size information. (Bug #22046353)

InnoDB: With innodb_autoinc_lock_mode=0, multiple threads waiting for a table-level lock caused an unexpected deadlock. (Bug #21983865, Bug #78761)

InnoDB: A race condition in trx_kill_blocking() raised an assertion. (Bug #21508537)

InnoDB: An OPTIMIZE TABLE operation on a table with a full-text index raised an assertion. (Bug #21378944)

InnoDB: A buffer pool load operation resulted in a “Cannot allocate 0 bytes” error. (Bug #21371070)

InnoDB: A FLUSH TABLES ... FOR EXPORT operation appeared to stall. A loop in the ibuf_contract_in_background function failed to exit. (Bug #21133329, Bug #77011)

InnoDB: A full-text query raised an assertion. Under certain circumstances, DDL operations such as ALTER TABLE ... RENAME caused full-text auxiliary tables to be removed on server restart. (Bug #13651665)

Replication: With gtid_mode=ON, executing an empty query before setting gtid_next made the latter action fail. It was because only statements that do not change the data can be executed before one can successfully change gtid_next, and an empty query was not considered one of those “safe” statements. This fix allows the setting of gtid_next after an empty query. (Bug #22811150)

Replication: Slaves running MySQL 5.7 could not connect to a MySQL 5.5 master due to an error retrieving the server_uuid, which is not part of MySQL 5.5. This was caused by changes in the method of retrieving the server_uuid. (Bug #22748612)

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

Replication: Setting certain semisynchronous-replication configurations on the master server when semisynchronous replication was not enabled on it might cause the server to exit. This fix prevents the unexpected exits to occur in the situation. (Bug #22602324)

Replication: The variable explicit_defaults_ts was not initialized during the construction of a Query_event object. That caused Valgrind warnings for dependency on an uninitialized variable. This fix makes sure the variable is initialized. (Bug #22110916, Bug #78999)

References: This issue is a regression of: Bug #18885916, Bug #72794.

Replication: In the next_event() function, which is called by a slave's SQL thread to read the next even from the relay log, the SQL thread did not release the relaylog.log_lock it acquired when it ran into an error (for example, due to a closed relay log), causing all other threads waiting to acquire a lock on the relay log to hang. With this fix, the lock is released before the SQL thread leaves the function under the situation. (Bug #21697821)

References: See also: Bug #20492319.

Replication: A partially failed statement was not correctly consuming an auto-generated or specified GTID when binary logging was disabled. The fix ensures that a partially failed DROP TABLE, a partially failed DROP USER or a partially failed DROP VIEW consume respectively the relevant GTID and save it into @@GLOBAL.GTID_EXECUTED and mysql.gtid_executed table when binary logging is disabled. (Bug #21686749)

Replication: When using row-based replication in a cascading or circular replication setup, where a master is replicating to server 1 which is then replicating to server 2, merge tables were not being correctly applied on server 2. This could cause an unexpected halt on server 2 while server 1 was unaffected. (Bug #17018343)

Replication: An intermittent ASan error was being reported on the rpl.rpl_checksum_cache test. The error reported was related to the binary log sender doing a heap-use-after-free on a given memory address. (Bug #78995, Bug #22109863)

Replication: mysqldump has been updated to make it compatible with multi-source replication. Now when replication channels other than the default channel are found, mysqldump --dump-slave outputs a CHANGE MASTER TO statement for each replication channel. (Bug #78467, Bug #21855705)

Replication: If a multi-threaded replication slave running with relay_log_recovery=1 stopped unexpectedly, during restart the relay log recovery process could fail. This was due to transaction inconsistencies not being filled, see Handling an Unexpected Halt of a Replication Slave. Prior to this fix, to recover from this situation required manually setting relay_log_recovery=0, starting the slave with START SLAVE UNTIL SQL_AFTER_MTS_GAPS to fix any transaction inconsistencies and then restarting the slave with relay_log_recovery=1. This process has now been automated, enabling relay log recovery of a multi-threaded slave upon restart automatically. (Bug #77496, Bug #21507981)

Fedora builds now are configured using -DMYSQL_MAINTAINER_MODE=0 to silence GCC 6 warnings. (Bug #23274249)

Allocation of a large number (2^20) of Performance Schema index statistic objects could cause a server exit. (Bug #23188107)

If the keyring_okv plugin configuration directory was missing, attempts to rotate the InnoDB master key could cause a server exit. (Bug #23149683)

INSERT with ON DUPLICATE KEY UPDATE and REPLACE on a table with a foreign key constraint defined failed with an incorrect “duplicate entry” error rather than a foreign key constraint violation error. (Bug #23135731)

References: This issue is a regression of: Bug #78853, Bug #22037930.

Contention in Performance Schema mutex instrumentation creation and destruction has been reduced, such that mutexes for which instruments are frequently created and destroyed are maintained in separate pages from those for which instruments are rarely created and destroyed. (Bug #22965826)

With certain build options, an uninitialized variable in get_key_scans_params() could produce a compilation error. (Bug #22916059)

Adding new tokens to the parser caused query digest values to change. (Bug #22906606)

For debug builds, CONCAT_WS() could raise an assertion if there was nothing to append. (Bug #22888420)

Fixed Valgrind warnings for failed LEAST() evaluations. (Bug #22883278)

INET_NTOA() could cause a server exit when producing an error message. (Bug #22881810)

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

The my_write() call could cause a server exit if it attempted to check the current connection and the connection had been killed. (Bug #22867809)

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

Invoking Enterprise Encryption functions in multiple threads simultaneously could cause a server exit. (Bug #22839278)

Setting log_syslog_tag to NULL could cause a server exit. (Bug #22834781)

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

If the expression for an indexed generated column contained an AND or OR operator, the optimizer could choose that index too often and create execution plans that produced incorrect results. (Bug #22810883)

CREATE TABLE statements in mysqlpump output could be missing KEY clauses and would not load. (Bug #22726732)

Attempting to use Enterprise Encryption functions after creating and dropping them could cause a server exit. (Bug #22669012)

Setting sort_buffer_size to a very large value could cause some operations to fail and result in a server exit. (Bug #22594514)

For an InnoDB table containing generated columns, using the table in a join could result in a server exit due to improper error checking. (Bug #22561845)

REPLACE on a table with an indexed generated column could cause a server exit if the index prefix length was calculated incorrectly. (Bug #22445211)

An UPDATE operation affecting a generated virtual BLOB column could cause a server exit. (Bug #22444212)

SHOW CREATE TABLE for a table containing a generated column could cause a server exit or produce an Illegal mix of collations error. (Bug #22392268)

On a slave server, replication of an UPDATE statement that updated an indexed BLOB virtual generated column of an InnoDB table could cause a server exit. (Bug #22241015)

An assertion could be raised when a deadlock occurred due to a SELECT ... GROUP BY ... FOR UPDATE query executed using a Loose Index Scan. (Bug #22187476)

mysqlpump could exit due to improper handling of error conditions in a dump thread. (Bug #22017120)

Several potential buffer overflow issues were corrected. (Bug #21977380, Bug #23187436, Bug #23202778, Bug #23195370, Bug #23202699)

If the CA certificate as given to the --ssl-ca option had an invalid path, yaSSL returned an error message different from OpenSSL. Now both return SSL connection error: SSL_CTX_set_default_verify_paths failed. (Bug #21920657)

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)

With show_compatibility_56=OFF, SHOW VARIABLES and SHOW STATUS statements having a WHERE clause did not work. (Bug #21783883)

The audit_log plugin failed to abort the current operation when told to do so by a plugin handler for a MYSQL_AUDIT_PARSE_PREPARSE event. (Bug #21457956)

Memory leaks reported by Valgrind for mysqlpump were fixed. (Bug #21237667)

Some string functions returned one or a combination of their parameters as their result. If one of the parameters had a non-ASCII character set, the result string had the same character set, resulting in incorrect behavior when an ASCII string was expected. (Bug #18740222)

On Fedora 24, upgrades using a Community MySQL Server RPM failed to replace an installed MariaDB Galera server due to a change in the MariaDB package. (Bug #81390, Bug #23273818)

The mysql_read_defaults_options() function was missing a break statement, causing any option value for the --ssl-cipher option also to be applied to the --tls-version option, with unpredictable results. (Bug #81139, Bug #23129821)

A DELETE from joined tables using a derived table in the WHERE clause failed if one of the joined tables was used in the derived table. (Bug #81014, Bug #23074801)

Compiling of clients that used the MySQL C API could fail if they used an obsolete path to mysql.h or <mysql/mysql.> and did not set the include path. This was due to use of #include <file_name> notation rather than #include "file_name" in internal MySQL header files, which have been adjusted. (Bug #80935, Bug #23047194)

MySQL did not compile under Solaris 12 using Sun Studio. To correct this, instances of __attribute__ were changed to MY_ATTRIBUTE. (Bug #80748, Bug #22932576)

The service_mysql_keyring.h and services.h header files misspelled mysql_keyring_service_st as mysql_keyring_file_service_st. (Bug #80688, Bug #22908232)

The fix for Bug #79194 did not cover the eq_ref access method, with the result that left joins could return incorrect results.

(Bug #80526, Bug #22833364)

References: This issue is a regression of: Bug #79194, Bug #22176604.

The sanity() macro in strings/decimal.c produced Valgrind warnings due to reading uninitialized buffer contents. (Bug #80461, Bug #22782203, Bug #22839915)

Starting the server with --initialize failed if the keyring_file_data system variable was also set at startup. To handle this, with --initialize the server no longer skips registration of plugins loaded with the --early-plugin-load option. (Bug #80451, Bug #22777039)

Loading the Rewriter query rewrite plugin when there was no query_rewrite database resulted in Valgrind warnings. (Bug #80333, Bug #22710312)

The optimizer transformed EXISTS (SELECT * ...) constructs to EXISTS (SELECT 1 ...) before all columns in the inner subquery had been resolved, which could result in rejection of valid queries that included a HAVING clause without GROUP BY in the subquery. (Bug #80231, Bug #22655856)

For a server compiled with -DWITH_PERFSCHEMA_STORAGE_ENGINE=0, a memory leak could occur for buffered log messages used during server startup. (Bug #80089, Bug #22578574)

A query could return incorrect results under these conditions: A column with a default value contained NULL; SELECT DISTINCT or a GROUP BY clause was used and the column containing the NULL value was part of the select list; an InnoDB temporary table was used during query processing. (Bug #79591, Bug #22343910)

A null pointer dereference of a parser structure could occur during stored procedure name validation. (Bug #79396, Bug #22286421)

Database initialization failed during installation using Ubuntu 15.10 packages. (Bug #79377, Bug #22252900)

mysql_upgrade failed to widen the User and Proxied_user columns in the mysql.proxies_priv system table from 16 to 32 characters. (Bug #78254, Bug #21762656)

Failure of UNINSTALL PLUGIN could lead to inaccurate or confusing errors for subsequent INSTALL PLUGIN operations. (Bug #74977, Bug #20085672)

mysqld_multi displayed misleading error messages when it was unable to execute my_print_defaults. (Bug #74636, Bug #19920049)

Previously, upgrading the server using an RPM package (including installation using yum) required upgrading the client package to the same MySQL version, which may be undesirable for some installations. This rule has been relaxed so that upgrading to a General Availability (GA) server version requires only that some GA client version be installed, which is less likely to require a client upgrade. (Bug #72230, Bug #18518216)

mysqldump failed silently with no error message when it encountered an error while executing FLUSH LOGS. (Bug #71783, Bug #18284273)

Configuration Notes

Packaging Notes

Security Notes

Functionality Added or Changed

Bugs Fixed

Incompatible Change: To load a keyring plugin, the --early-plugin-load option is used. Previously, the default --early-plugin-load option value was the name of the keyring_file plugin library file. Now the default value is empty.

[mysqld]
early-plugin-load=keyring_file.so

(Bug #80413, Bug #22748738)

The obsolete support-files/MySQL-shared-compat.spec.sh file was removed from MySQL distributions. (Bug #22525609)

InnoDB: The InnoDB tablespace encryption feature, which provides at-rest data encryption for InnoDB tables, now supports Oracle Key Vault for encryption key management. Oracle Key Vault support relies on the keyring_okv plugin which is available in MySQL Enterprise Edition. A secure and robust encryption key management solution such as OKV is critical for security and for compliance with various security standards. For more information, see InnoDB Tablespace Encryption.

The linked OpenSSL library for the MySQL Commercial Server has been updated to version 1.0.1s. For a description of issues fixed in this version, see http://www.openssl.org/news/vulnerabilities.html.

This change does not affect the Oracle-produced MySQL Community build of MySQL Server, which uses the yaSSL library instead. (Bug #22685885, Bug #22923458)

MySQL Enterprise Edition now includes a keyring_okv plugin that uses Oracle Key Vault for keyring backend storage. For more information, see The MySQL Keyring.

For queries with many OR conditions, the optimizer now is more memory-efficient and less likely to exceed the memory limit imposed by the range_optimizer_max_mem_size system variable. In addition, the default value for that variable has been raised from 1536000 to 8388608. (Bug #79450, Bug #22283790)

InnoDB; Partitioning: INSERT and SELECT statements against a partitioned InnoDB table having generated columns were not always handled correctly. (Bug #22444530)

References: See also: Bug #21776494, Bug #21824564, Bug #21864838.

InnoDB: An error was returned on startup when a replication slave attempted to access an encrypted table. The server UUID used to compose the master key name was not persisted to the tablespace data file, resulting in the use of an incorrect master key. (Bug #22912582)

InnoDB: In debug builds, an unnecessary buf_block_align() call could cause a latching order violation. A DML operation resulted in a page mismatch assertion due to the same buf_block_align() call. (Bug #22709463, Bug #21321238)

InnoDB: An ALTER TABLE ... ADD COLUMN operation on a table with virtual columns raised an assertion. (Bug #22650296)

InnoDB: An unnecessary comparison in tablespace encryption code caused compiler warnings. (Bug #22645816)

InnoDB: INNODB_SYS_TABLESPACES could report incorrect ALLOCATED_SIZE and FILE_SIZE values for a general tablespace created outside of the data directory. The i_s_dict_fill_sys_tablespaces() function generated an incorrect remote file path. (Bug #22590095, Bug #80070)

InnoDB: In debug builds, an update operation on a table with virtual columns raised an assertion. (Bug #22572997)

InnoDB: Modifications were made to InnoDB code to handle warnings when compiling with Microsoft Visual Studio 2015. (Bug #22542547, Bug #79964)

InnoDB: Running REPLACE operations on multiple connections resulted in a hang. (Bug #22530768, Bug #79185)

InnoDB: Operations relating to tabespace encryption resulted in a hang on FreeBSD. (Bug #22520464, Bug #79901)

InnoDB: MySQL stalled when synchronizing the InnoDB full-text index cache. (Bug #22516559, Bug #16510576, Bug #73816)

InnoDB: A CREATE TABLE ... DATA DIRECTORY operation failed to create a table while innodb_flush_method was set to O_DIRECT. (Bug #22180006, Bug #79200)

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

InnoDB: In debug builds, a buffer pool resizing operation resulted in a segmentation violation. The buf_pool_resizing variable was not protected. (Bug #22179317)

InnoDB: The innodb_open_files setting could exceed the open files limit. (Bug #22111472)

InnoDB: InnoDB attempted crc32 checksum validation instead of innodb after a crc32 checksum validation failure, causing repeated crc32 checksum validation attempts. Checksum validation order is now optimized dynamically.

Thanks to Daniel Black for the patch. (Bug #79725, Bug #22452597)

Replication: When a slave with no binary log connected to a group replication master, it failed with Error running query, but no information about the failure was available from the output of SHOW SLAVE STATUS or in the replication_applier_status_by_worker table. (Bug #22699395)

Replication: Setting relay_log_recovery=1 generated an error during recovery, due to repositories not being initialized. (Bug #22523554)

Replication: Issuing STOP SLAVE caused a spurious Error reading packet from server: Lost connection to MySQL server during query message to be written to the error log. With this fix, when connection to the master is lost, the abort_slave flag is checked and the error message is printed only if the flag is not set. (Bug #22305605, Bug #79504)

References: See also: Bug #12977988, Bug #22290309.

Replication: When the binary log was disabled, the GTID specified by gtid_next when committing an empty transaction caused by a BEGIN statement was saved in gtid_executed when it should not have been. This did not occur when the binary log was enabled.

Now, when gtid_next is set for the current session, BEGIN raises an ER_CANT_DO_IMPLICIT_COMMIT_IN_TRX_WHEN_GTID_NEXT_IS_SET error inside any transaction regardless of whether binary logging is enabled, since this statement causes an implicit commit. In this case, the GTID specified by gtid_next is not saved in gtid_executed. (Bug #22130929)

Replication: When replication was configured but not started on a slave, the variable currently_executing_gtid was not properly initialized, but it would be used if the performance_schema table replication_applier_status_by_worker was queried, causing assertion failures and pointer issues. With this fix, the variable is now properly initialized at the construction of the Relay_log_info object. (Bug #21953132, Bug #78722)

Replication: RESET SLAVE ALL could delete a channel even when master_pos_wait and wait_until_sql_thread_after_gtid were still waiting for transactions to be applied. This could cause a MySQL server exit when the functions tried to access the channel that was deleted. Now, a channel reference counter was added that is increased if the channel should not be deleted when the functions are running. RESET SLAVE ALL will wait for no reference, and then it will delete the channel. (Bug #21842399, Bug #78445)

Replication: When relay_log_recovery=1, a slave server, at its initialization, still tried to scan the relay log files in order to update Retrieved_Gtid_Set and the transaction parser state, which was an unnecessary waste of resources because the slave I/O thread would just be initialized to the SQL thread position in the new relay log file. With this fix, the slave server skips scanning the relay log files when relay_log_recovery=1. (Bug #21798355, Bug #78352)

Replication: XA transactions were not handled correctly when --gtid-mode=ON and the binary log was disabled. It was because on both master and slave servers, the GTID state was sometimes not saved and the GTID ownership was sometimes not cleaned up. This fix makes sure those steps are now properly performed. (Bug #21618727)

References: See also: Bug #22165138, Bug #77740, Bug #21452916.

Replication: When a multi-threaded slave stopped with an error, the same error message was printed three times. Now, the SQL thread's kill acceptance status is saved, and only printed once. (Bug #21198611, Bug #77237)

Replication: When using a multi-threaded slave with relay_log_info_repository set to TABLE, the slave applier thread failed to write XA transactions to the worker configuration. (Bug #20988291)

Replication: mysqlbinlog --verbose displayed BINARY and VARBINARY data as ordinary strings, causing any single quote (“'”) or backslash (“\”) among the data to be printed as such, which was confusing to the users and, in the case of a backslash, caused the next character to be skipped. This fix makes mysqlbinlog print the characters' hexadecimal values (“\x27” for single quote and “\x5c” for backslash) instead. (Bug #20836250)

Replication: The test case main.merge failed when the variables binlog_format was set to “ROW,” as the server tried to get information for table creation for a child table before it was opened. With this fix, the server skips getting information for the table in the situation. (Bug #20574550, Bug #75976)

Replication: When a server was run with relay_log_info_repository=TABLE and the --super-read-only option enabled, a statement which caused an update to the slave info tables, such as STOP SLAVE or CHANGE MASTER TO, resulted in a 'STOP SLAVE' failed: 1290: The MySQL server is running error, preventing the statement being executed. The fix ensures that replication operations are permitted regardless of the setting of read_only and super_read_only. (Bug #78963, Bug #22097534)

Replication: Valgrind tests of mysqlbinlog revealed some memory leaks. (Bug #78223, Bug #21697461, Bug #78966)

Replication: If a query on a master generated an error and partial results were written to the binary log, for example due to a DROP TABLE IF EXISTS statement applying to multiple tables that would break foreign key constraints, when a slave configured with replication filters encountered the query it could be incorrectly binary logged. This caused errors such as:

Last_SQL_Error: Query caused different errors on master and slave. Error on master: message (format)='Cannot delete or update a parent row: a foreign key constraint fails' error code=1217 ; Error on slave: actual message='no error', error code=0. Default database: 'db1'. Query: 'DROP TABLE IF EXISTS `table1` /* generated by server */'

There were two fixes required for this bug.

(Bug #77684, Bug #21435502)

References: See also: Bug #20797764, Bug #76493.

RTRIM() on large strings could be very slow. (Bug #22884187)

References: This issue is a regression of: Bug #18315770, Bug #12368495.

Integer overflow could occur during client handshake processing, leading to a server exit. (Bug #22722946)

Missing initializers in the query plan constructor resulted in Valgrind warnings. (Bug #22573117)

mysqlpump failed (syntax error) when a view name contained a space character. View names are now quoted. (Bug #22505474)

UNHEX() with an invalid argument could result in garbage characters in the warning message. (Bug #22358933)

Improper host name checking in X509 certificates could permit man-in-the-middle attacks. (Bug #22295186, Bug #22738607)

For debug builds, when an indexed nonnullable generated column with an empty string generated expression was updated during an insert for a duplicated key, there was an optimization that resulted in the server failing to find the duplicated index, causing an assertion to be raised. (Bug #22195364)

A boolean mode full-text search caused a segmentation fault. (Bug #22176795)

Queries on generated columns that used WITH ROLLUP could raise an assertion. (Bug #22131343)

For a prepared statement that used a derived table, an assertion could be raised at execute time when checking statement privileges. (Bug #22108567)

Concurrent selecting and flushing of a FEDERATED table while killing connections accessing it could result in a server exit. (Bug #21918190)

For debug builds, when a query using join buffering and one of the tables inserted into the join buffer was accessed using a dynamic range scan on an index containing a virtual column, a Valgrind error occurred when writing columns to the join buffer. (Bug #21872184)

After iterations of uninstalling and installing the audit_log plugin, the server could hang. (Bug #21796658)

With a LOCK TABLES statement in effect, access to Performance Schema tables could fail, as could SHOW STATUS with show_compatibility_56=OFF. (Bug #21789221)

Executing GRANT PROXY statements after altering the definition of the mysql.user system table could result in a server exit. (Bug #21699037)

Certain error messages included part of the SQL statement that produced them, possibly exposing data. (Bug #21682356)

Although it is possible to create nontemporary tables using the prefix #sql, Performance Schema assumed that tables named using this prefix were temporary and could be ignored. Performance Schema now uses table attributes other than the name to identify temporary tables. (Bug #21105475, Bug #22532368, Bug #79934)

Account filtering performed by the audit_log plugin incorrectly used the account named by the USER() function rather than the CURRENT_USER() function (the latter being the account used for authentication). (Bug #19509471, Bug #22454245, Bug #77553)

NAME_CONST() can return null if incorrect arguments are given. In some cases, this was not handled and could cause a server exit. (Bug #19143243)

Character set conversion operations on NULL parameters to prepared statements could cause a server exit. (Bug #18823979)

Loose Index Scan was not chosen for queries that had an equality condition. (Bug #18109609)

Long or complex SQL statements could cause the parser to run out of memory. The new parser_max_mem_size system variable now enables control over the maximum amount of memory available to the parser. The default value places no limit on memory available, but the value can be reduced to protect against out-of-memory situations. (Bug #14744160)

A Valgrind warning for memory_free_noop() was silenced. (Bug #80457, Bug #22782197)

The MySQL server failed to start if built with the -m32 option on Solaris/Sparc, due to improper static data alignment in init_delegates(). (Bug #80445, Bug #22763880)

The plugin_keyring.h header file misspelled st_mysql_keyring as st_mysql_keyring_file. (Bug #80414, Bug #22748867)

For shared-memory connections on Windows, the client library opened a handle on a mutex but did not close it. Subsequent attempts to restart the server on the other end of the connection failed if the client still had the mutex handle open. (Bug #80234, Bug #22646779)

mysqld attempted to initialize plugins specified using the --early-plugin-load option when the --help option was specified. (Bug #80077, Bug #22573767)

ALTER USER IDENTIFIED WITH ... expired the account password, even if the authentication plugin did not support password expiration. (Bug #79999, Bug #22551523)

Some Performance Schema global instruments, if not enabled at server startup, could be in a state where it was not possible to enable them at runtime. This restriction has been lifted. Affected instruments include mutex, rwlock, cond, and socket instances.

Thanks to Zhang Yingqiang for the patch. (Bug #79784, Bug #22517278, Bug #66515, Bug #14532176)

Setting the super_read_only system variable at server startup had no effect. (Bug #79328, Bug #22233503)

These audit_log plugin issues were corrected:

(Bug #79079, Bug #22136709, Bug #79091, Bug #22142166, Bug #79092, Bug #22142209, Bug #21783798)

For INSERT and UPDATE operations that caused FOREIGN KEY constraint violations, errors were reported rather than warnings when the IGNORE keyword was used. (Bug #78853, Bug #22037930)

References: See also: Bug #23135731.

Using the server session service, executing an SQL statement from a thread with no VIO context could raise an assertion. (Bug #78734, Bug #21959409)

Error messages raised by JSON_KEYS() and JSON_EXTRACT() contained the wrong data. (Bug #78699, Bug #22026278)

CREATE VIEW statements that used the TIMESTAMPDIFF() function with MICROSECOND as the unit resulted in incorrect view definitions. (Bug #78506, Bug #21877062)

For an existing user, CREATE USER IF NOT EXISTS produced an error rather than a warning. Similarly, for an nonexisting user, ALTER USER IF EXISTS produced an error rather than a warning. (Bug #78374, Bug #21807286)

For some queries, an Index Merge access plan was chosen over a range scan when the cost for the range scan was the same or less. (Bug #77209, Bug #21178196)

UNHEX() could attempt a left shift of a negative number. (Bug #73964, Bug #19642015)

EXPLAIN for SELECT ... FOR UPDATE statements acquired locks. (Bug #72858, Bug #18899860)

Processlist state information was not updated correctly for LOAD DATA INFILE and could show a state different from executing. (Bug #69375, Bug #16912362)

Compilation Notes

Data Type Notes

Installation Notes

Packaging Notes

Security Notes

Functionality Added or Changed

Bugs Fixed

A value of system is now permitted for the WITH_BOOST CMake option. If this option is not set or is set to system, it is assumed that the correct version of Boost is installed on the compilation host in the standard location. In this case, the installed version of Boost is used rather than any version included with a MySQL source distribution. (Bug #22224313)

In addition to the mysql-5.7.11.tar.gz source tarball, another tarball named mysql-boost-5.7.11.tar.gz is provided. The new tarball contains everything in the first tarball, but also contains all the required Boost header files in a subdirectory named boost. This is for the benefit of those who do not have the correct Boost version installed and do not wish to or cannot download it. To build from this source distribution, add -DWITH_BOOST=boost to the CMake command line.

Bit functions and operators comprise BIT_COUNT(), BIT_AND(), BIT_OR(), BIT_XOR(), &, |, ^, ~, <<, and >>. Currently, bit functions and operators require BIGINT (64-bit integer) arguments and return BIGINT values, so they have a maximum range of 64 bits. Arguments of other types are converted to BIGINT and truncation might occur.

A planned extension for MySQL 8.0 is to permit bit functions and operators to take binary string type arguments (BINARY, VARBINARY, and the BLOB types), enabling them to take arguments and produce return values larger than 64 bits. Consequently, bit operations on binary string arguments in MySQL 5.7 might produce different results in MySQL 8.0. To provide advance notice about this potential change in behavior, the server now produces warnings for bit operations for which binary string arguments will not be converted to integer in MySQL 8.0. These warnings afford an opportunity to rewrite affected statements. To explicitly produce MySQL 5.7 behavior in a way that will not change after an upgrade to 8.0, cast bit-operation binary string arguments to convert them to integer. For more information and examples, see Bit Functions and Operators.

Previously, mysqld --initialize required the data directory to not exist or, if it existed, to be empty. Now an existing data directory is permitted to be nonempty if every entry either has a name that begins with a period (.) or is named using an --ignore-db-dir option. (Bug #79250, Bug #22213873)

Packaging support for Ubuntu 15.10 was added. (Bug #79104, Bug #22147191)

The linked OpenSSL library for the MySQL Commercial Server has been updated from version 1.0.1p to version 1.0.1q. For a description of issues fixed in this version, see http://www.openssl.org/news/vulnerabilities.html.

This change does not affect the Oracle-produced MySQL Community build of MySQL Server, which uses the yaSSL library instead. (Bug #22348181)

The default value of the default_password_lifetime system variable that controls the global password expiration policy has been changed from 360 (360 days) to 0 (no password expiration). The default of 360 sometimes took people by surprise when account passwords expired a year after upgrading to MySQL 5.7. To continue to use a value other than 0 as the password expiration, start the server with an explicit setting for default_password_lifetime. For example, use these lines in an option file:

[mysqld]
default_password_lifetime=360

(Bug #77277, Bug #21284761)

MySQL Server now supports a keyring service that enables internal server components and plugins to securely store sensitive information for later retrieval. The implementation includes a keyring_file plugin that stores keyring data in a file local to the server host. For more information, see The MySQL Keyring, Writing Keyring Plugins, and The Keyring Service.

MySQL client programs now support an --ssl-mode option that enables you to specify the security state of the connection to the server. Permitted option values are PREFERRED (establish a secure encrypted connection if the server supports the capability, falling back to an unencrypted connection otherwise), DISABLED (establish an unencrypted connection), REQUIRED (establish a secure connection, or fail), VERFIFY_CA (like REQUIRED, but additionally verify the server certificate), VERIFY_IDENTITY (like VERIFY_CA, but additionally verify that the server certificate matches the host name to which the connection is attempted). For backward compatibility, the default is PREFERRED if --ssl-mode is not specified.

These clients support --ssl-mode: mysql, mysqladmin, mysqlbinlog, mysqlcheck, mysqldump, mysqlimport, mysqlshow, mysqlpump, mysqlslap, mysqltest, mysql_upgrade.

The --ssl-mode option comprises the capabilities of the client-side --ssl and --ssl-verify-server-cert options. Consequently, both of those options are now deprecated and will be removed in a future MySQL release. Use --ssl-mode=REQUIRED instead of --ssl=1 or --enable-ssl. Use --ssl-mode=DISABLED instead of --ssl=0, --skip-ssl, or --disable-ssl. Use --ssl-mode=VERIFY_IDENTITY instead of --ssl-verify-server-cert options. (The server-side --ssl option is not deprecated.)

For the C API, the new MYSQL_OPT_SSL_MODE option for mysql_options() corresponds to the --ssl-mode option. The MYSQL_OPT_SSL_ENFORCE and MYSQL_OPT_SSL_VERIFY_SERVER_CERT options for mysql_options() correspond to the client-side --ssl and --ssl-verify-server-cert options. They are now deprecated and will be removed in a future MySQL release. Use MYSQL_OPT_SSL_MODE with an option value of SSL_MODE_REQUIRED or SSL_MODE_VERIFY_IDENTITY instead.

For more information, see Command Options for Secure Connections, and mysql_options().

In consequence of this change, the minor C API version number was incremented.

InnoDB: A new InnoDB configuration option, innodb_tmpdir, allows you to configure a separate directory for temporary files created during online ALTER TABLE operations that rebuild the table. This option was introduced to help avoid MySQL temporary directory overflows that could occur as a result of large temporary files created during online ALTER TABLE operations. innodb_tmpdir can be configured dynamically using a SET statement.

Online ALTER TABLE operations that rebuild a table also create an intermediate table file in the same directory as the original table. The innodb_tmpdir option is not applicable to intermediate table files. (Bug #19183565)

InnoDB: InnoDB now supports at-rest data encryption for InnoDB tables stored in file-per-table tablespaces. Encryption is enabled by specifying the ENCRYPTION option when creating or altering an InnoDB table. For more information, see InnoDB Tablespace Encryption.

Replication: The log_statements_unsafe_for_binlog variable was added to provide control over whether the warnings generated by error 1592 are added to the binary log or not.

yaSSL was upgraded to version 2.3.9. This upgrade corrects an issue in which yaSSL handled only cases of zero or one leading zeros for the key agreement instead of potentially any number, which in rare cases could cause connections to fail when using DHE cipher suites. (Bug #22361038)

The Valgrind function signature in mysql-test/valgrind.supp was upgraded for Valgrind 3.11. (Bug #22214867)

The audit_log plugin now produces events in the MYSQL_AUDIT_TABLE_ACCESS_CLASS class. These events are abortable. (Bug #21458192)

The format of log output produced by mysqld_safe now is configurable using the --mysqld-safe-log-timestamps option. This option can be used to produce log timestamps in formats compatible with the server or in formats used by mysqld_safe in older versions of MySQL. For more information, see mysqld_safe — MySQL Server Startup Script. (Bug #78475, Bug #21862951)

The server now supports an --early-plugin-load option that indicates which plugins to load before loading mandatory built-in plugins and before storage engine initialization. One use for this option is to load the keyring_file plugin: The InnoDB storage engine uses the keyring tablespace encryption, so the keyring_file plugin must be loaded early to ensure that it is available prior to InnoDB initialization.

Storage engines now can request notification about acquisition and release of exclusive metadata locks. As result, the LOCK_STATUS column of the metadata_locks Performance Schema table has two new status values. The PRE_ACQUIRE_NOTIFY and POST_RELEASE_NOTIFY status values are brief and signify that the metadata locking subsubsystem is notifying interested storage engines while entering lock acquisition or leaving lock release operations.

The mysql_plugin utility is deprecated and will be removed in a future version of MySQL. Alternatives include loading plugins at server startup using the --plugin-load or --plugin-load-add option, or at runtime using the INSTALL PLUGIN statement.

The mysql_kill(), mysql_list_fields(), mysql_list_processes(), and mysql_refresh() C API functions are deprecated and will be removed in a future version of MySQL. The same is true of the corresponding COM_PROCESS_KILL, COM_FIELD_LIST, COM_PROCESS_INFO, and COM_REFRESH client/server protocol commands. Instead, use mysql_query() to execute a KILL, SHOW COLUMNS, SHOW PROCESSLIST, or FLUSH statement, respectively.

InnoDB; Partitioning: When OPTIMIZE TABLE rebuilt a partitioned InnoDB table, it placed the resulting partition tablespace files (*.ibd files) in the default data directory instead of the directory specified using the DATA DIRECTORY option. (Bug #75112, Bug #20160327)

InnoDB: InnoDB failed to update index statistics when adding or dropping a virtual column. (Bug #22469660, Bug #79775)

InnoDB: A small InnoDB buffer pool size with a large innodb_stats_persistent_sample_pages setting resulted in a Difficult to find free blocks in the buffer pool warning. (Bug #22385442)

InnoDB: memcached connections are blocked from accessing tables that contain an indexed virtual column. Accessing an indexed virtual column requires a callback to the server, but a memcached connection does not have access to the server code. (Bug #22384503, Bug #79691)

InnoDB: InnoDB did not return an informative message when refusing an online ALTER TABLE operation that attempted to add an index and a virtual column. (Bug #22374827)

InnoDB: An invalid innodb_saved_page_number_debug setting caused a server exit. (Bug #22311319, Bug #79516)

InnoDB: InnoDB failed to free a table object when a compressed table and temporary compressed table were created in the same shared tablespace. (Bug #22306581)

InnoDB: In NUMA-related code, the size information passed to the mbind() call in the buf_chunk_init() function was incorrect. (Bug #22293530, Bug #79434)

InnoDB: NUMA support was incomplete for online buffer pool resizing operations. (Bug #22293511, Bug #79354)

InnoDB: A SELECT COUNT(*) query that counted the results of a full-text subquery raised an assertion. (Bug #22270139)

InnoDB: InnoDB passed a buffer with an incorrect TINYBLOB data length for a virtual column, resulting in a purge thread failure. (Bug #22256752)

InnoDB: A purge failure occurred while deleting data from a table that contained a spatial index. (Bug #22230442, Bug #22366370)

InnoDB: An assertion was raised when purge accessed a freed page while attempting to rebuild virtual column data from the clustered index. (Bug #22204260)

InnoDB: Only prefix bytes were logged for an indexed virtual column, resulting in an a Clustered record for sec rec not found error. (Bug #22202788)

InnoDB: A small buffer pool with an innodb_page_size setting of 64K could cause startup, bootstrap, and recovery failures. (Bug #22179133, Bug #79201)

InnoDB: Unreachable code that checks for 32-bit file offsets was removed. (Bug #22163880, Bug #79150)

InnoDB: A slow shutdown failure was caused by background threads adding undo records to the purge history list during or after purge thread exit. (Bug #22154730)

InnoDB: The InnoDB purge thread died attempting to purge a virtual column index record that was not delete-marked. (Bug #22141031)

InnoDB: In debug builds, an ALTER TABLE operation that increased the column length of a virtual column raised an assertion. (Bug #22139917)

InnoDB: ut_allocator prepended the allocation payload with a 12-byte header on 32-bit systems, causing unaligned memory access. On 32-bit SPARC systems, the unaligned memory access caused a crash during bootstrap. (Bug #22131684)

InnoDB: In debug builds, an ALTER TABLE operation that added a new virtual column before an existing virtual column raised an assertion. (Bug #22123674, Bug #22111464)

InnoDB: InnoDB startup messages related to dumping and loading of the buffer pool were improved. (Bug #22096661, Bug #78960)

InnoDB: Support was enabled for ALGORITHM=INPLACE operations that add an index on an existing virtual column while dropping another virtual column. Support was also enabled for ALGORITHM=INPLACE operations that add a virtual column and an index. When adding an index on a newly-added virtual column, purge now skips the uncommitted virtual index. (Bug #22082762)

InnoDB: The wrong table object was used to compute virtual column values for a query that accessed multiple instances of the same table. (Bug #22070021)

InnoDB: A purge thread failure occurred when inserting and deleting spatial data. The child page number field was not stored during the R-tree search stage. (Bug #22027053)

InnoDB: Starting the server with an empty innodb_data_home_dir entry in the configuration file caused InnoDB to look for the buffer pool file in the root directory, resulting in a startup error. (Bug #22016556, Bug #78831)

InnoDB: A failure to compute virtual column values caused an excessive number of error messages. (Bug #21968375)

InnoDB: An INFORMATION_SCHEMA.INNODB_CMP_PER_INDEX query raised an assertion. A dictionary mutex was taken while InnoDB populated an in-memory heap table. The mutex was not released before InnoDB attempted to convert the in-memory heap table to an optimized internal temporary table. (Bug #21950756, Bug #78714)

InnoDB: To avoid a potential hang and redo log overwrite, the innodb_log_file_size minimum value was increased from 1MB to 4MB, and the length calculation in log_margin_checkpoint_age() was revised. (Bug #21924224, Bug #78647)

InnoDB: A full-text query run under high concurrency caused a server exit due to an invalid memory access. (Bug #21922532)

InnoDB: An ALTER TABLE operation on a table partitioned across multiple tablespaces moved existing partitions to the table's default tablespace, resulting in an assertion on SHOW CREATE TABLE. Likewise, ALTER TABLE tbl_name TABLESPACE tablespace_name moved existing partitions to the named tablespace. Only ALTER TABLE ... REORGANIZE PARTITION should move existing partitions to the table's default tablespace or to a named tablespace. Running ALTER TABLE tbl_name TABLESPACE tablespace_name on a table partitioned across multiple tablespaces should only change the table's default tablespace. (Bug #21914047, Bug #22124042, Bug #79030)

InnoDB: With a large innodb_sort_buffer_size setting, adding an index on an empty table performed more slowly than expected. (Bug #21762319, Bug #78262)

InnoDB: A race condition occurred between fil_names_write() and file_rename_tablespace_in_mem(). (Bug #21549928)

InnoDB: Purge attempted to access undo pages that were freed by a preceding undo log truncate operation, resulting in an assertion. (Bug #21508627)

InnoDB: InnoDB did not return an informative message when refusing an online ALTER TABLE operation on a table with a spatial index. (Bug #20111575)

InnoDB: A compiler barrier was added to ut_relax_cpu(). The ut_always_false dummy global variable was removed from ut_delay(). (Bug #20045167, Bug #74832)

InnoDB: Incorrect index values were returned while dropping a virtual column. The altered table object was used to evaluate virtual column values. (Bug #79773, Bug #22469459)

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

Partitioning: Subquery scans on partitioned tables with virtual columns could leak memory. (Bug #79145, Bug #22162200)

Replication: The behavior of SET GTID_PURGED was not consistent between version 5.6 and 5.7. The fix ensures that version 5.7 does not initiate a transaction for SET GTID_PURGED statements. (Bug #21472492)

Replication: When DML invokes a trigger or a stored function that inserts into an AUTO_INCREMENT column, that DML has to be marked as an unsafe statement. If the tables are locked in the transaction prior to the DML statement (for example by using LOCK TABLES), then the DML statement was not being marked as an unsafe statement. The fix ensures that such DML statements are marked correctly as unsafe. (Bug #17047208)

Replication: If pseudo_slave_mode was set to 1 while an XA transaction was in the prepare stage, an assert was generated. The fix ensures that changes from 0 to 1 can be made during XA transactions. Note that this variable is solely for internal use by the server. (Bug #79416, Bug #22273964, Bug #78695, Bug #21942487)

Replication: When using GTIDs, a GTID-violating statement generates an error in the following cases:

The error prevented the implicit pre-commit, which caused a race condition. This has been fixed by making the error not prevent the implicit pre-commit from happening. This matches the expected behavior for GTID-violating DDL statements to implicitly commit the previous transaction before executing it. (Bug #78543, Bug #21895421)

Replication: When a slave was configured with log_bin=OFF, the applier (SQL) thread was failing to correctly roll back partial transactions left in the relay log. The fix ensures that on reconnection, the applier thread correctly rolls back a partial transaction and starts applying it again from the next relay log file. (Bug #78211, Bug #21691396)

Replication: If the server stopped unexpectedly immediately before committing an XA transaction which had been prepared, and the transaction modified the mysql.gtid_executed table, then the subsequent recovery aborted due to an innodb_lock_wait_timeout error when it was reading the mysql.gtid_executed table. To fix the problem, XA transactions are no longer permitted to modify the mysql.gtid_executed table. (Bug #77740, Bug #21452916)

Replication: As part of the fix for Bug #16290902, when writing a DROP TEMPORARY TABLE IF EXISTS query into the binary log, the query is no longer preceded by a USE `db` statement. Instead the query uses a fully qualified table name, for example DROP TEMPORARY TABLE IF EXISTS `db`.`t1`;. This changed the application of replicate-rewrite-db filter rules, as they work only on the default database specified in a USE statement. This caused slaves to fail when the resulting CREATE TEMPORARY TABLE was applied. The fix ensures that at the time of writing a DROP TEMPORARY TABLE IF EXISTS query into the binary log, a check is made for the default database. If it exists then the query is written as USE default_db in the binary log. If a default database is not present then the query is logged with the qualified table name. (Bug #77417, Bug #21317739)

Replication: If generating a GTID for a transaction fails, the transaction is not written to the binary log but still gets committed. Although running out of GTIDs is a rare situation, if it did occur an error was written to the binary log as a sync stage error. With binlog_error_action=ABORT_SERVER, the server aborts on such an error, avoiding data inconsistency. When binlog_error_action=IGNORE_ERROR, the server continues binary logging after such an error, potentially leading to data inconsistency between the master and the slave. The fix changes the error to be correctly logged as a flush stage error. (Bug #77393, Bug #21276561)

Replication: When using --gtid-mode=on , --enforce-gtid-consistency , and --binlog-format=row, if a user defined function with multiple DROP TEMPORARY TABLE statements was executed on a master, the resulting binary log caused an error on slaves. The fix ensures that stored functions and triggers are also considered multi-statement transactions, and that when --enforce-gtid-consistency is enabled, functions with CREATE TEMPORARY TABLE or DROP TEMPORARY TABLE statements generate an ER_GTID_UNSAFE_CREATE_DROP_TEMPORARY_TABLE_IN_TRANSACTION error. (Bug #77354, Bug #21253415)

Replication: Stored procedure local variables that were used in an ALTER EVENT statement were not being replicated correctly. This was related to the fact that CALL statements are not written into the binary log. Instead each statement executed in a stored procedure is binary logged separately, with the exception that the statement string is modified so that uses of stored procedure local variables are replaced with NAME_CONST('spvar_name', 'spvar-value') calls. DDL statements (which are always binary logged in statement binary log mode irrespective of the current binary log format) can also use stored procedure local variables and a clash could cause them to not be replicated correctly. The fix ensures that any stored procedure local variables used in a statement are replaced with NAME_CONST(...), except for the case when it is a DML statement and the binary log format is ROW. (Bug #77288, Bug #21229951)

Replication: DROP TABLE statements are regenerated by the server before being written to the binary log. If a table or database name contained a non-regular character, such as non-latin characters, the regenerated statement was using the wrong name, breaking replication. The fix ensures that in such a case the regenerated name is correctly converted back to the original character set. Also during work on this bug, it was discovered that in the rare case that a table or database name contained 64 characters, the server was throwing an assert(M_TBLLEN < 128) assertion. The assertion has been corrected to be less than or equal 128. (Bug #77249, Bug #21205695)

References: See also: Bug #78036, Bug #22261585, Bug #21619371.

Replication: Irrespective of the current binlog_format setting, DDL that changes metadata on a master is always identified and written to the binary log in STATEMENT format. Such DDL could occur from event based SQL statements, such as CREATE EVENT or DROP EVENT, or transactions that had unsafe functions such as sysdate(). When binlog_format=MIXED and attempting to replicate such DDL, it was not being correctly identified and therefore was not being correctly replicated. (Bug #71859, Bug #19286708)

The System-V initialization script for RHEL6 or older failed to enable the mysqld service by default. (Bug #22600974)

Some activations of triggers that referenced a NEW value inside a query might cause a server exit. (Bug #22377554)

Parsing the output of ST_GeometryType() as a DATETIME value with a default character set of utf32 caused a server exit. (Bug #22340858)

For a character set loaded from an XML file, the server could fail to properly initialize its state map, leading to a server exit. (Bug #22338946)

Inserting a token of 84 4-byte characters into a full-text index raised an assertion. The maximum token length was 84 characters up to a maximum of 252 bytes, which did not account for 4-byte characters. The maximum byte length is now 336 bytes. (Bug #22291765, Bug #79475)

For some combination of consumers, the Performance Schema prepared statement instrumentation could cause a server exit. (Bug #22291560)

If a client attempted to use an unsupported client character set (ucs2, utf16, utf32), the error message reported to the client differed for SSL and non-SSL connections. (Bug #22216715)

Data corruption or a server exit could occur if a stored procedure had a variable declared as TEXT or BLOB and data was copied to that variable using SELECT ... INTO syntax from a TEXT or BLOB column. (Bug #22203532, Bug #22232332, Bug #21941152)

For debug builds, with the ONLY_FULL_GROUP_BY SQL mode disabled, the optimizer could attempt to sort on outer references, causing an assertion to be raised. (Bug #22200984)

Different handling of YEAR values for INSERT and SELECT could raise an assertion when such values were used in a generated-column expression. (Bug #22195458)

For debug builds, for queries involving MIN() or MAX() on an indexed column and a reference to an unindexed datetime column, the optimizer could attempt to access unread values, causing an assertion to be raised. (Bug #22186926)

Geohash decoding (for example, for ST_LongFromGeoHash(), ST_LatFromGeoHash(), and ST_PointFromGeoHash()) could yield incorrect results due to the rounding algorithm being too aggressive. (Bug #22165582)

In debug builds, with READ UNCOMMITTED transaction isolation level, a SELECT reading a generated column using an index could raise an assertion. (Bug #22133710)

For generated columns, the optimizer could fail to establish the proper table reference, resulting in a server exit. (Bug #22132822)

For some combination of consumers, the Performance Schema file instrumentation could fail due to an attempt to use a NULL pointer while instrumenting temporary file I/O. (Bug #22130453)

The Performance Schema could raise an assertion based on the (incorrect) assumption that instrumenting a temporary file open operation always resulted in an instrumented file. (Bug #22118669)

An ALTER TABLE statement that added an index on a virtual generated column using the INPLACE algorithm did not properly report warnings (or errors in strict SQL mode) for problems with virtual column values. Any subsequent ALTER TABLE on the same table using the COPY algorithm produced such warnings (or failures in strict SQL mode) due to evaluating the problematic value, but left the connection in a state that made further INPLACE alterations on the table fail for the same reason. (Bug #22095783)

If the left expression of an IN expression was a row subquery that accesses no tables, an assertion could be raised (in debug builds), or incorrect results could be returned (in release builds). (Bug #22089623)

Expressions that match an indexed generated column may be replaced with the generated column by the optimizer to enable use of the associated index. However, this optimization was not performed for single-table update and delete statements. The optimizer now extends this replacement optimization to such statements. (Bug #22077611)

ANSI SQL mode could cause inconsistencies in processing of generated column expressions. (Bug #22018979)

Removal of server session plugins was faulty and could cause a server exit. (Bug #21983102)

For some queries, if the optimizer used Disk-Sweep Multi-Range Read optimization on generated columns, the server could exit. (Bug #21980430)

mysqlpump tries to do as much work in parallel as possible, but the dump threads lacked a synchronization point before backing up the data, resulting in inconsistent backup. mysqlpump now locks the server and flushes all the tables using FLUSH TABLES WITH READ LOCK to ensure that any further connections view the same state of all the databases.

This change lifts the restriction aginst the --single-transaction option being mutually exclusive with parallelism. When using --single-transaction, it is no longer necessary to disable parallelism by setting --default-parallelism to 0 and not using any instances of --parallel-schemas. (Bug #21980284)

A fault in pthread_rwlock_unlock() wherein it decremented the lock counter even for already unlocked objects could result in deadlock. (Bug #21966621)

The Performance Schema could acquire a double lock on session system variables, causing a server hang or (in debug builds) an assertion to be raised. (Bug #21935106)

Certain queries containing WHERE 0 of the following form could cause a server exit due to uninitialized reads: SELECT (SELECT col AND constant FROM t WHERE 0) IN (SELECT constant FROM t1). (Bug #21922202)

CREATE TEMPORARY TABLE .. SELECT statements involving BIT columns that resulted in a column type redefinition could cause a server exit or an improperly created table. (Bug #21902059)

For UPDATE operations on InnoDB tables, there could be a mismatch between the value of a virtual generated column in the index and the value in the “before” buffer, resulting in a server exit. (Bug #21875520)

With character_set_server=utf16le, some values of ft_boolean_syntax could cause a server exit for full-text searches. (Bug #21631855)

With gtid_mode=ON, concurrent execution of SHOW TABLE STATUS and REVOKE ALL PRIVILEGES could lead to deadlock in there was a view in the database and REVOKE ALL PRIVILEGES failed for some but not all of the named users. (Bug #21463167)

mysqlpump could exit due to incorrect synchronization of view-handling threads during dump processing. (Bug #21399236, Bug #21447753)

With LOCK TABLES in force, an attempt to open a temporary MERGE table consisting of a view in its list of tables (not the last table in the list) caused a server exit. (Bug #20691429)

For certain prepared statements, the optimizer could transform join conditions such that it used a pointer to a temporary table field that was no longer available after the initial execution. Subsequent executions caused a server exit. (Bug #19941403)

Repeated execution of ALTER TABLE v1 CHECK PARTITION as a prepared statement, where v1 is a view, led to a server exit.

In addition, output for some administrative operations, when they are attempted on a view, changes from “Corrupt” to “Operation failed”. These include ANALYZE TABLE, OPTIMIZE TABLE, and REPAIR TABLE, and ALTER TABLE statements that perform ANALYZE PARTITION, CHECK PARTITION, OPTIMIZE PARTITION, and REPAIR PARTITION operations. (Bug #19817021)

Valgrind detected some possibly unsafe use of string functions in code used for asymmetric encryption. (Bug #19688135)

An out-of-memory failure in join buffer allocation could lead to incorrect results for multiple-table queries. (Bug #19031409)

SSL connections ignored any change made by passing the MYSQL_OPT_READ_TIMEOUT option to the mysql_options() C API function. (Bug #17618162)

For ALTER TABLE statements, the parser did not support the ALGORITHM clause for some operations involving tablespaces or partitions. (Bug #17400320)

Debian packages create the root user account using the auth_socket authentication plugin to achieve secure-by-default installation if installation was done with a blank root password. However, auth_socket was being used even if the password was not blank. (Bug #80137, Bug #22594846, Bug #23321113, Bug #81518)

Solaris packages failed to note the dependency of the MySQL client library on the libstlport library. (Bug #79778, Bug #22504264)

Thread handle resource leakage could occur when creating threads for handling connections on Windows, which could lead to Windows servers eventually running out of handles. (Bug #79714, Bug #22455198)

Using systemd to start mysqld failed if configuration files contained multiple datadir lines. Now the last datadir line is used. (Bug #79613, Bug #22361702)

A derived table contained in the SET clause of an UPDATE statement should be materialized to avoid an error about updating a table that is also read in the same statement. Materialization did not occur for some statements, leading to that error. (Bug #79590, Bug #22343301)

MySQL 5.7.8 prohibited references to select list columns of the outer query from the HAVING clause of a correlated subquery in the inner query because they are not permitted by standard SQL. However, because this is a frequently used extension, it is once again permitted. (Bug #79549, Bug #22328395)

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

Installing just shared libraries, clients, and development support files failed to install everything needed to build client applications because the binary_log_types.h header file was not installed. (Bug #79531, Bug #22321338)

SHOW CREATE TRIGGER could fail to display all applicable SQL modes. (Bug #79526, Bug #22313133)

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

On SELinux, mysqld --initialize with an --init-file option could fail to initialize the data directory. (Bug #79442, Bug #22314098, Bug #79458, Bug #22286481)

Syntax checks were not always performed when an ALTER TABLE statement changed a column's type from TEXT to JSON. This could lead to JSON columns containing invalid JSON data. This issue was observed when the original TEXT column used the utf8mb4_bin collation. (Bug #79432, Bug #22278524)

Hexadecimal and bit literals written to saved view definitions could be truncated. This could also affect extended EXPLAIN output. (Bug #79398, Bug #22268110)

ST_Buffer() returned an error for geometries with an SRID different from 0. Nonzero SRID values now are permitted but ignored (calculations are still done using Cartesian coordinates). (Bug #79394, Bug #22306745)

A regression caused failure of the workaround at Restrictions on Subqueries for avoiding ER_UPDATE_TABLE_USED errors when referencing the same table in a subquery as was used as target for an UPDATE or DELETE statement. (Bug #79333, Bug #22239474)

Statements causing multiple parse errors could cause an assertion to be raised. (Bug #79303, Bug #22222013)

Some queries with derived tables perform better with materialization than when merged into the outer query. The optimizer no longer uses merging by default for derived tables containing dependent subqueries in the select list. (Bug #79294, Bug #22223202)

ALTER USER and SET PASSWORD did not work at server startup when invoked in the file named using the --init-file option. (Bug #79277, Bug #22205360)

When not in strict SQL mode, attempts to implicitly insert NULL into a NOT NULL column resulted in different behavior depending on whether the table had a trigger. (Bug #79266, Bug #22202665)

Some replication-only code was not protected with #ifdef and failed to compile with the WITH_UBSAN CMake option enabled. (Bug #79236, Bug #22190632)

Configuring MySQL with the -DWITH_UBSAN=ON CMake option resulted in spurious runtime warnings from comp_err. These are now suppressed. Also, a CMake warning was added that undefined behavior address sanitizer support is currently experimental. (Bug #79230, Bug #22190656)

INSERT INTO ... SELECT statements could insert values other than DEFAULT into generated columns. (Bug #79204, Bug #22179637)

With the derived_merge flag of the optimizer_switch system variable enabled, queries that used a derived table on the inner side of an outer join could return incorrect results. (Bug #79194, Bug #22176604)

References: See also: Bug #80526, Bug #22833364.

Memory leaks in libmysqld were corrected. (Bug #79187, Bug #22174219)

FOUND_ROWS() could return a negative value if the preceding query was a UNION involving SQL_CALC_FOUND_ROWS and LIMIT ... OFFSET. (Bug #79131, Bug #22155786)

IN-to-EXISTS subquery transformation could cause SELECT NULL IN (subquery) to return 0 rather than NULL.

IN-to-EXISTS subquery transformation could yield incorrect results for queries for which the table was nonempty, the subquery on the left side of the IN predicate produced an empty result, and semi-join optimization was disabled. (Bug #78946, Bug #22090717, Bug #74403, Bug #19822406)

The result from WEIGHT_STRING() could be incorrect when used in a view. (Bug #78783, Bug #21974321)

For connections made using a Unix socket file, specifying the --ssl-ca option caused the connection to fail. (Bug #78509, Bug #21878661)

If server was started with --thread-handling=no-threads, no foreground thread was created for a client connection. The Performance Schema did not account for the possibility of no foreground threads for queries on the session_connect_attrs table, causing an assertion to be raised. (Bug #78292, Bug #21765843)

mysqlpump generated incorrect INSERT statements for tables that had generated columns. (Bug #78082, Bug #21650559)

ALTER TABLE ... CONVERT TO CHARACTER SET operations that used the INPLACE algorithm were ineffective if the table contained only numeric data types. Also, such operations failed to clean up their temporary .frm file. (Bug #77554, Bug #21345391)

Heavy SHOW PROCESSLIST or SELECT ... FROM INFORMATION_SCHEMA.PROCESSLIST activity could result in the server accepting more than max_connections connections. (Bug #75155, Bug #20201006)

When used with the libmysqld embedded server, the mysql_stmt_execute() C API function failed with a malformed communication packet error, even for simple prepared statements. (Bug #70664, Bug #17883203)

Queries using SUM(DISTINCT) could produce incorrect results when there were many distinct values. (Bug #56927, Bug #11764126, Bug #79648, Bug #22370382)

Security Notes

Functionality Added or Changed

Bugs Fixed

Previously, MySQL supported only the TLSv1 protocol for encrypting secure connections. TLS support is now extended to enable a higher level of encrypted connection security:

Because TLSv1.2 requires OpenSSL, support for this protocol is available in binary distributions only for MySQL Commercial Server, and not for MySQL Community Server (which is compiled using yaSSL). To enable TLSv1.2 support if you build from source, you must set the WITH_SSL CMake option to use OpenSSL.

The tls_version system variable enables specifying at startup the TLS protocols permitted by the server. On the client side, the --tls-version option enables specifying the TLS protocols permitted per client invocation.

The new MASTER_TLS_VERSION option for the CHANGE MASTER TO statement specifies the encryption protocols permitted by the master for slave connections.

The mysql_options() C API function has a new MYSQL_OPT_TLS_VERSION option that enables specifying from within the client library the TLS protocols permitted by a client program.

By default, MySQL attempts to use the highest TLS protocol version available, depending on which SSL library was used to compile the server and client, which key size is used, and whether the server or client are restricted from using some protocols; for example, by means of tls_version/--tls-version.

For more information, see Secure Connection Protocols and Ciphers.

InnoDB: Enabling the new innodb_background_drop_list_empty debug configuration option helps avoid test case failures by delaying table creation until the background drop list is empty. (Bug #21891560)

InnoDB: The innodb_support_xa system variable, which enables support for two-phase commit in XA transactions, is deprecated. InnoDB support for two-phase commit in XA transactions is always enabled as of MySQL 5.7.10. Disabling innodb_support_xa is no longer permitted as it makes replication unsafe and prevents performance gains associated with binary log group commit.

These client programs now support the --enable-cleartext-plugin option: mysqlcheck, mysqldump, mysqlimport, mysqlshow. This option enables the mysql_clear_password cleartext authentication plugin. (See The Cleartext Client-Side Authentication Plugin.) (Bug #21235226)

These functions now produce warnings for invalid input: UNHEX(), INET_NTOA(), INET_ATON(), INET6_NTOA(), INET6_ATON(). Also, INET_ATON() now returns NULL and produces a warning for arguments that contain more than four groups of digits. (Bug #78856, Bug #22042027, Bug #78884, Bug #22071558)

MySQL distributions now include lz4_decompress and zlib_decompress utilities that can be used to decompress mysqlpump output that was compressed using the --compress-output=LZ4 and --compress-output=ZLIB options. For more information, see lz4_decompress — Decompress mysqlpump LZ4-Compressed Output, and zlib_decompress — Decompress mysqlpump ZLIB-Compressed Output. (Bug #78108, Bug #21644479)

mysql_upgrade now attempts to print more informative errors than FATAL ERROR: Upgrade failed. (Bug #77803, Bug #21489398)

InnoDB: When attempting to create a cascading foreign key constraint on a primary key column used in a virtual index, the error message that was returned did not include information from dict_foreign_has_col_in_v_index(). (Bug #22050059)

InnoDB: An in-place operation that rebuilt a table with multiple indexed virtual columns raised an assertion. (Bug #22018532)

InnoDB: A SELECT ... FOR UPDATE operation on a table that only contained virtual columns and a virtual column index raised an invalid assertion. (Bug #21981164, Bug #21880930)

InnoDB: The calculation in dict_index_node_ptr_max_size() that determines the maximum index record size treated fixed fields that exceeded the maximum column length as fixed-size fields instead of variable length fields. (Bug #21968191)

InnoDB: A server exit during a TRUNCATE TABLE operation on a table with a full-text index caused startup to fail. (Bug #21959479)

InnoDB: An ALTER TABLE ... DISCARD TABLESPACE operation raised an invalid assertion. (Bug #21957001, Bug #78728)

InnoDB: Compared to previous releases, small tablespaces containing tables with BLOB values had larger data files due to regression introduced in MySQL 5.7.5. (Bug #21950389, Bug #78623)

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

InnoDB: The ord_part flag was not reset after a failed operation to create an index on a virtual column, causing InnoDB to assert on a subsequent insert operation. (Bug #21941320, Bug #21979969)

InnoDB: An invalid search tuple was created for a table with virtual columns. (Bug #21922176)

InnoDB: InnoDB attempted to purge a virtual column index record that was not marked for deletion. (Bug #21901389)

InnoDB: Successive open table operations on tables with virtual columns caused a memory access violation. (Bug #21894654)

InnoDB: Update vector generation for a full-text search DOC_ID did not initialize a new ufield, resulting in an assertion. (Bug #21891185)

InnoDB: InnoDB failed to prevent foreign key SET NULL or CASCADE constraints on virtual column base columns and virtual index columns. (Bug #21890816)

InnoDB: An invalid comparison raised an assertion under a 64k innodb_page_size setting. (Bug #21882024, Bug #78516)

InnoDB: When estimating the maximum record size of a b-tree index page, InnoDB incorrectly treated long-length fixed fields (greater than 767 bytes) as fixed-size fields instead of variable length fields. (Bug #21880445)

InnoDB: In debug builds, dtuple_get_n_fields attempted to read freed memory that was previously allocated for a virtual column tuple, resulting in a server exit. (Bug #21875974)

InnoDB: Selecting from INNODB_CMPMEM with option big-tables=1 raised a buffer pool mutex assertion. (Bug #21871451, Bug #78494)

InnoDB: InnoDB returned an invalid corruption-related error message during an IMPORT TABLESPACE operation. (Bug #21838158, Bug #77321)

InnoDB: After a crash on Windows, copying the data directory to a non-Windows platform to perform the restore caused a crash recovery failure on startup. The code did not convert file path separators from “\” to “/” in the redo log. (Bug #21825127, Bug #78410)

InnoDB: A FLUSH TABLE ... FOR EXPORT operation asserted in row_quiesce_table_start() when run on a partitioned table with partitions residing in a system or general tablespace. (Bug #21796845)

InnoDB: A DROP TABLE operation resulted in a server exit. The return value of a function call was not checked, which lead to dereferencing of a null pointer. The patch for this bug also addresses a potential race condition. (Bug #21794102, Bug #78336)

InnoDB: In debug builds, an ordered scan across multiple partitions did not use a priority queue, resulting in an assertion. (Bug #21753477)

InnoDB: After restarting the server, the COMPRESSION column of the INNODB_SYS_TABLESPACES table displayed incorrect data. The COMPRESSION column was removed from INNODB_SYS_TABLESPACES. To view the current setting for page compression, use SHOW CREATE TABLE. (Bug #21687636, Bug #78197)

InnoDB: An invalid table flags value raised an assertion. The SYS_TABLES.MIX_LEN(flags2) value was not read for tables that use ROW_FORMAT=REDUNDANT. (Bug #21644827)

InnoDB: An assertion was raised when crash recovery handling of an MLOG_TRUNCATE redo log record treated a shared tablespace as a file-per-table tablespace. Redo was skipped for the shared tablespace. (Bug #21606676)

InnoDB: Transaction rollback after recovery failed due to an invalid assertion. (Bug #21575121)

InnoDB: Insufficient information in the undo log about spatial columns raised an assertion and could result in a upgrade failure. Consequently, a slow shutdown is required prior to performing an in-place upgrade from MySQL 5.7.8 or 5.7.9 to 5.7.10 or higher. For more information, refer to Changes Affecting Upgrades to MySQL 5.7. (Bug #21508582)

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

InnoDB: A secondary index is not permitted on a virtual column that is based on a foreign key-referenced column that uses ON DELETE CASCADE, ON DELETE SET NULL, ON UPDATE CASCADE, or ON UPDATE SET NULL. The restriction was not enforced. (Bug #21508402, Bug #77843)

InnoDB: A duplicate key error that occurred during an online DDL operation reported an incorrect key name. (Bug #21364096, Bug #77572)

InnoDB: An ALTER TABLE operation caused the server to exit on disk full. (Bug #21326304, Bug #77497)

InnoDB: The system tablespace data file did not extend automatically when reaching the file size limit, causing startup to fail with a size mismatch error and preventing the addition of another system tablespace data file. (Bug #21287796, Bug #77128)

InnoDB: Altering the letter case of a column introduced an inconsistency between the frm file and data dictionary resulting in a failed CREATE INDEX operation on the altered column. (Bug #20755615)

InnoDB: An ALTER TABLE operation that converted a table to an InnoDB file-per-table tablespace did not check for unknown files with the same name as the destination .idb file, permitting an unknown file of the same name to be overwritten. (Bug #19218794, Bug #73225)

InnoDB: row_merge_read_clustered_index() did not handle a bulk load error correctly. (Bug #19163625)

Partitioning: Partition scans did not evaluate virtual generated columns properly. This could cause issues with partitioned tables having an index on a virtual BLOB column. (Bug #21864838, Bug #21881155)

Partitioning: While executing CHECK TABLE, when checking whether rows were in the correct partition, the partition engine missed updates for virtual generated columns. (Bug #21779554)

Partitioning: Performing an in-place ALTER TABLE on a partitioned InnoDB table having one or more partitions which used a separate tablespace could cause the server to fail. (Bug #21755994)

Partitioning: When all partitions were pruned, they were not initialized for scanning during initialization of indexes. This involved two related issues, one being that the active index was not set back to the maxmimum key value when the index was closed. In addition, when this occurred as part of a multi-range read, there were attempts to access unset variables. (Bug #78260, Bug #21754608, Bug #21620577)

Replication: On a multi-threaded slave configured with master_info_repository=TABLE and relay_log_info_repository=TABLE which had previously been run with autocommit=1, if the slave was stopped and autocommit changed to 0, executing START SLAVE caused the session to appear to hang. After the lock wait timeout, when START SLAVE proceeded the server would stop unexpectedly. The fix ensures that when master_info_repository=TABLE, relay_log_info_repository=TABLE, and autocommit=0 a new transaction is generated for start and commit to avoid deadlocks. (Bug #21440793)

Replication: Fatal errors encountered during flushing or synchronizing the binary log were being ignored. Such errors are now caught and handled depending on the setting of binlog_error_action. (Bug #76795, Bug #68953, Bug #20938915, Bug #16666407)

If the server was started with --performance_schema_accounts_size=0, querying the Performance Schema status variable tables caused a server exit. (Bug #22131713)

For debug builds, using ALTER TABLE to add a generated column to a table could cause a deadlock. (Bug #22083048)

The systemd unit file did not specify any --pid-file option for mysqld, with the result that server startup could fail. The unit file now includes a default --pid-file option in the ExecStart value. This default can be overridden in the override.conf file by changing both PIDFile and ExecStart to specify the PID file path name. (Bug #22066787)

A query with nested derived tables and scalar subqueries in the select list of the derived tables might in some cases cause a server exit. (Bug #22062023)

When mysqld was run with --initialize, it used chown() to set the data directory owner, even if ownership was already correct. This caused problems for AppArmor and SELinux. The server now checks whether the data directory owner is correct and skips the chown() call if so. (Bug #22041387)

Failed evaluation of a generated column expression for CREATE TABLE or ALTER TABLE could cause a server exit. Now if expression evaluation causes truncation or provides incorrect input to a function, the statement terminates with an error and the DDL operation is rejected. (Bug #22018999)

Creating a unique index on a virtual POINT column could result in an error or assertion for later table accesses. (Bug #22017616)

Sending a load spike to a newly started server could cause the Performance Schema to allocate a large amount of memory, possibly leading to out-of-memory failure. (Bug #22006088)

A missing error check could result in a server exit for DELETE statements that referred to user-defined variables. (Bug #21982313)

Possible buffer overflow from incorrect use of strcpy() and sprintf() was corrected. (Bug #21973610)

MySQL RPM packages for RHEL5 failed to create the mysql system user. (Bug #21950975)

MySQL does not support columns of ROW type, but the server did not prevent generated columns from being created that used ROW expressions. These are now prohibited. (Bug #21940542)

The version_tokens plugin called the locking service using a timeout value of only one second. The timeout is now taken from the default value of the lock_wait_timeout system variable (that is, one year). (Bug #21928198)

Spatial functions could return invalid results if given a polygon or multipolygon argument containing holes such that a hole vertex touched the exterior ring at a point lying in the interior of an exterior ring segment. This could manifest itself as: ST_UNION() producing an invalid polygon; ST_SymDifference() producing an invalid multipolygon; ST_Intersection() producing an invalid self-intersecting polygon; ST_Difference() producing an invalid geometry. (Bug #21927733, Bug #21927639, Bug #21927558, Bug #21977775)

With the STRICT_TRANS_TABLES SQL mode enabled, it was not possible to insert data into a VIRTUAL generated column defined with the NOT NULL attribute. (Bug #21927469)

Problems leading to Valgrind warnings for OpenSSL random number generation were corrected. (Bug #21927436)

Querying views on Windows could lead to memory leaks. (Bug #21908206)

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

Generated column definitions specified with the NULL attribute resulted in a syntax error. (Bug #21900170)

A stored procedure that used ST_Area() could return different numbers of rows for the first and second executions. (Bug #21889842)

For polygon values with an interior ring that touches an exterior ring, ST_Buffer() could return invalid polygon values. (Bug #21871856)

Two rows in the threads Performance Schema table could have the same THREAD_OS_ID value. (Bug #21865330)

For debug builds, using ALTER TABLE to change the expression for a generated column could cause a server exit. (Bug #21854004)

ALTER USER failed if the server was started with --skip-grant-tables. (Bug #21847825)

Performance Schema reads of a session's THD structure while the session was running could create race conditions and result in a server exit. (Bug #21841412)

A prepared statement that computes ST_IsSimple() or ST_Buffer_Strategy() on a nullable column in an outer join could return different numbers of rows for the first and second statement executions. (Bug #21841051)

Queries on the variables_by_thread Performance Schema table could cause a server exit when examining the system variables of a new connection. (Bug #21840950)

Spatial functions could read already freed memory. (Bug #21823135)

For Debian package control files, libnuma-dev was added to Build-Depends to enable NUMA support. (Bug #21822631)

Selecting DECIMAL values into user-defined variables could cause a server exit. (Bug #21819304)

Re-evaluation of a generated column expression could cause access to previously freed memory and a server exit. (Bug #21810529)

ST_SymDifference() could raise an assertion for polygons with self-intersection points. (Bug #21767301, Bug #79031, Bug #22124757)

USER field output from the audit log plugin was malformed. (Bug #21766380)

A server exit could occur for queries for which a) a GROUP BY included primary key and secondary key columns; and b) the WHERE clause included an equality predicate on the first primary key column where that column was constant. (Bug #21761044)

Building MySQL using parallel compilation sometimes failed with an attempt to compile sql_yacc.yy before lex_token.h had been created. (Bug #21680733)

With binary logging enabled, issuing DROP TEMPORARY TABLE when in XA_IDLE state caused an assertion to be raised. Now an ER_XAER_RMFAIL error is returned.

In consquence of the fix for this issue, statements that previously succeeded in XA_IDLE state now fail with an ER_XAER_RMFAIL error. When running with --gtid-mode=ON, an explicit DROP continues to fail with ER_GTID_UNSAFE_CREATE_DROP_TEMPORARY_TABLE_IN_TRANSACTION. (Bug #21638823)

A query with a subquery in the left-hand part of an IN subquery that was transformed into a semi-join might cause a server exit. (Bug #21606400)

Concurrent FLUSH PRIVILEGES and REVOKE or GRANT statements could produce a small time window during which invalid memory access to proxy user information could occur, leading to a server exit. (Bug #21602056)

Using WITH ROLLUP within a subquery could cause a server exit. (Bug #21575790)

For debug builds, a call to MAKE_SET() with a subquery as argument might be evaluated before tables were locked, causing an assertion to be raised. (Bug #21547779)

Starting the server with the query_alloc_block_size system variable set to certain negative values on a machine without enough memory could result in out-of-memory errors. (Bug #21503595)

Using UNINSTALL PLUGIN to uninstall the daemon_example plugin could cause a server exit. (Bug #21467458)

FLUSH DES_KEY_FILE failed to reload the DES key file. (Bug #21370329)

If an error occurred during the setup phase of subquery materialization used to compute an IN predicate, cleanup of the temporary table did not happen, leading to Valgrind errors. (Bug #21346081)

On Windows, the sysbench benchmark tool's "run" command would hang when attempting to create multiple tables for the OLTP test when using shared memory connections. (Bug #21319192, Bug #77481)

Queries rejected by MySQL Enterprise Firewall were truncated to 512 characters when written to the error log. (Bug #20948270)

A server exit could occur for the second execution of a prepared statement for which an ORDER BY clause referred to a column position. (Bug #20755389)

Repeated execution of a prepared statement could cause a server exit if the default database was changed. (Bug #20447262)

mysql_plugin could exit due to improper checking of string operation operands. (Bug #20376670)

After failure to create a temporary table during join processing and releasing the table descriptor, an attempt to access the now-invalid descriptor could cause a server exit. (Bug #19918299)

Type conversion failure for DECIMAL values could cause a server exit. (Bug #19912326, Bug #20013538)

INSERT DELAYED could cause a server exit for tables partitioned with a character column as the key and for which the expression required a character set conversion. (Bug #19894161)

A server exit could occur when updating a view using an ALL comparison operator on a subquery that selects from an indexed column in the main table. (Bug #19434916)

With AddressSanitizer (ASAN) enabled, triggers that contained null or invalid characters could cause an ASAN server exit. (Bug #18831513)

Incorrect error checking for the NAME_CONST() function could lead to a server exit. (Bug #17733850)

On SELinux, mysqld --initialize with an --init-file option could fail to initialize the data directory. Although fixed in 5.7.11, the Fedora 23 and EL6 5.7.10 RPM's were also updated with the fix; as a *-5.7.10-2-*.rpm release to the Yum repository. (Bug #79442, Bug #22314098, Bug #22286481)

INSERT ... ON DUPLICATE KEY UPDATE could result in a memory leak when executed as a prepared statement. (Bug #79122, Bug #22151233)

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

Queries that needed to store the result of ST_AsWKB() in a temporary table could fail with an error message. (Bug #79060, Bug #22131961)

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

If mysqld was started with the --help option, it created a binary log index file. If that file was located in the data directory and the command preceded data directory initialization, initialization then failed due to a nonempty data directory. (Bug #78986, Bug #22107047)

Some of the source files for spatial functions in the sql directory took excessive compile time and required too much compiler memory allocation. (Bug #78900, Bug #22078874)

Internal buffer sizes in resolve_stack_dump were increased to accommodate larger symbol space requirements for C++ code. (Bug #78885, Bug #22071592)

Problems leading to Valgrind warnings for libmysqld were corrected. (Bug #78819, Bug #22007587)

MySQL development RPM packages could fail to install if MySQL Connector/C development RPM packages were installed. (Bug #78815, Bug #22005375)

mysqladmin --help displayed the old-password command, even though the command itself was removed in MySQL 5.7.5. (Bug #78774, Bug #21972941)

The filename character set is intended for internal use, but references to it in SQL statements did not produce an error. Now they do. (Bug #78732, Bug #21958734)

If a generated column used an expression that is affected by the SQL mode, the expression could produce different results for the same input values, depending on the current SQL mode. (For example, interpretation of the || operator depends on the PIPES_AS_CONCAT SQL mode.) Now expression evaluation uses the SQL mode in effect at the time the column is defined. (Bug #78665, Bug #21929967)

Casting large hexadecimal values could produce an incorrect result and no truncation warning. (Bug #78641, Bug #21922414)

mysqlpump generated incorrect ALTER TABLE statements for adding foreign keys. (Bug #78593, Bug #21907297)

The error message returned when trying to define a BLOB, TEXT, JSON, or GEOMETRY column with a default value (Error 1101, ER_BLOB_CANT_HAVE_DEFAULT) referred to BLOB and TEXT columns only. The same error applies to any of these four types when trying to use the DEFAULT option with it in a column definition; the corresponding error message now makes this clear by referring to JSON and GEOMETRY columns as well. (Bug #78527, Bug #21887035)

A query using JSON_EXTRACT() returned the wrong result after a virtual index was added to the table. (Bug #78464, Bug #21854241)

Executing HELP statements or statements involving the CONVERT_TZ() function could lead to a memory leak and to MyISAM reference-count errors at server shutdown. (Bug #78443, Bug #21840241)

MySQL did not recognize functional dependencies from base columns in a generated column expression to the generated column. (Bug #78377, Bug #21807579)

It was possible to store non-ASCII data in columns intended to store data of character set ascii. (Bug #78276, Bug #21774967)

Adding a SPATIAL index to a MyISAM table could cause the cardinality of other indexes to become incorrect. (Bug #78213, Bug #21789000)

MySQL could fail to compile on Solaris 11.3 when /usr/gnu/bin/as was used as the linker. (Bug #77797, Bug #21484716)

Some punctuation characters in the armscii8 character set are represented by two encodings, with the result that a character stored using one encoding would not be found using a search with the other encoding. For such characters, MySQL now selects the encoding with the lowest value to consistently map instances onto the same encoding. (Bug #77713, Bug #21441405)

Item_copy_decimal::copy() did not take the div_precision_increment system variable value into account, resulting in DECIMAL values being returned with incorrect precision from some queries. (Bug #77634, Bug #21462523)

For queries with implicit grouping; an index with a string column as its first part; and a WHERE clause with an equality comparison comparing the column to a string with trailing characters in addition to the column value, an aggregate function that should return NULL returned non-NULL. (Bug #77480, Bug #21318711)

LOAD_FILE() could cause a server exit for some pathnames if the character set was cp932. (Bug #76555, Bug #20819220)

References: See also: Bug #51893.

For constructs such as ORDER BY numeric_expr COLLATE collation_name, the character set of the expression was treated as latin1, which resulted in an error if the collation specified after COLLATE is incompatible with latin1. Now when a numeric expression is implicitly cast to a character expression in the presence of COLLATE, the character set used is the one associated with the named collation. (Bug #73858, Bug #20425399)

Audit Log Notes

C API Notes

Compilation Notes

Packaging Notes

Performance Schema Notes

Plugin Notes

Security Notes

Spatial Data Support

sys Schema Notes

Functionality Added or Changed

Bugs Fixed

Some events cannot be terminated. Previously, if an audit plugin returned nonzero status for a nonterminable event, the server ignored the status and continued processing the event. However, if an audit plugin used the my_message() function to terminate a nonterminable event, a server exit occurred. Now the server correctly handles termination of nonterminable events using my_message(). (Bug #21458066)

Incompatible Change: The mysql_options() C API function has two new options, MYSQL_OPT_MAX_ALLOWED_PACKET and MYSQL_OPT_NET_BUFFER_LENGTH, that set the max_allowed_packet and net_buffer_length system variables, respectively. Each option name also now can be passed to the mysql_get_option() C API function to retrieve its value. For more information, see mysql_options(), and mysql_get_option().

The (undocumented) mysql_get_parameters() function has been removed. Applications that attempt to use it will get link errors and should be modified to use mysql_options() and mysql_get_option() instead.

One affected application is DBD::mysql, the MySQL driver for the Perl DBI. Upgrade to DBD::mysql 4.033 or higher, which includes a fix for the C API change just described. (Bug #20821550)

References: See also: Bug #20686665.

Previously, it was necessary to call mysql_thread_end() for each mysql_thread_init() call to avoid a memory leak. C API internals have been reimplemented to reduce the amount of information allocated by mysql_thread_init() that must be freed by mysql_thread_end():

(Bug #20621281, Bug #21802367)

Support for building using Microsoft Visual Studio 2015 was added. Changes include using the native (added in VS 2015) timespec library if it exists, renamed lfind/lsearch and timezone/tzname to avoid redefinition problems, set TMPDIR to "" by default as P_tmpdir no longer exists, deprecated std::hash_map in favor of std::unordered_map, and added Wix Toolset 3.10 support. (Bug #21657078)

MySQL distributions now contain a mysqlclient.pc file that provides information about MySQL configuration for use by the pkg-config command. This enables pkg-config to be used as an alternative to mysql_config for obtaining information such as compiler flags or link libraries required to compile MySQL applications. For more information, see Building C API Client Programs Using pkg-config.

A new INSTALL_PKGCONFIGDIR CMake option is available to specify the directory in which to install the mysqlclient.pc file. The default value is INSTALL_LIBDIR/pkgconfig, unless INSTALL_LIBDIR ends with /mysql, in which case that is removed first. (Bug #76131, Bug #20637746)

The shell and Perl versions of mysql_install_db have been removed from MySQL distributions. The executable C++ version of mysql_install_db implemented in MySQL 5.7.5 is still present, but remains deprecated (use mysqld --initialize instead) and will be removed in a future MySQL release. (Bug #21625471)

The deprecated _r versions of the libmysqlclient libraries are no longer installed. (Bug #21311067)

Two changes were made regarding the effect of show_compatibility_56:

For additional information about the effects of show_compatibility_56 and migration issues, see Server System Variables, and Migrating to Performance Schema System and Status Variable Tables. (Bug #21606701)

These Performance Schema tables now are world readable and accessible without the SELECT privilege: global_variables, session_variables, global_status, and session_status. An implication of this change is that SHOW VARIABLES and SHOW STATUS no longer require privileges on the underlying Performance Schema tables from which their output is produced when show_compatibility_56=OFF. (Bug #21251297)

With the show_compatibility_56 system variable enabled, the reported values of the Last_query_cost and Last_query_partial_plans status variables were incorrect.

With the show_compatibility_56 system variable disabled, the reported values of the Created_tmp_tables, Handler_external_lock, and Table_open_cache_% status variables were incorrect. (Bug #20483278, Bug #21788549, Bug #21788887)

Previously, the transaction instrument in the setup_instruments table was disabled by default, and the events_transactions_current and events_transactions_history consumers in the setup_consumers table were enabled by default. This setup is inconsistent, and having the consumers enabled could lead to the impression that transactions were instrumented by default. Now, the consumers are also disabled by default. To monitor transactions, enable the instrument and the applicable consumers. (Bug #78311, Bug #21780891)

With the show_compatibility_56 system variable disabled, SHOW VARIABLES and SHOW STATUS statements failed if MySQL was compiled without Performance Schema support. Consequently, it is no longer possible to compile without the Performance Schema. If it is desired to compile without particular types of instrumentation, that can be done with the following CMake options:

DISABLE_PSI_COND
DISABLE_PSI_FILE
DISABLE_PSI_IDLE
DISABLE_PSI_MEMORY
DISABLE_PSI_METADATA
DISABLE_PSI_MUTEX
DISABLE_PSI_PS
DISABLE_PSI_RWLOCK
DISABLE_PSI_SOCKET
DISABLE_PSI_SP
DISABLE_PSI_STAGE
DISABLE_PSI_STATEMENT
DISABLE_PSI_STATEMENT_DIGEST
DISABLE_PSI_TABLE
DISABLE_PSI_THREAD
DISABLE_PSI_TRANSACTION

For example, to compile without mutex instrumentation, configure MySQL using the -DDISABLE_PSI_MUTEX=1 option. (Bug #78159, Bug #21669500)

The session_account_connect_attrs Performance Schema table had mistakenly been changed to require the SELECT privilege. It requires no special privileges again. (Bug #77702, Bug #21436364)

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

In the setup_timers table, a CYCLE timer for ARM64 platforms is now available. (Bug #77620, Bug #21374923)

The Performance Schema now includes these instruments for monitoring I/O on binary log and relay log cache files:

wait/io/file/sql/binlog_cache
wait/io/file/sql/binlog_index_cache
wait/io/file/sql/relaylog_cache
wait/io/file/sql/relaylog_index_cache

In addition, the default value of performance_schema_max_file_classes has been increased from 50 to 80. (Bug #76225, Bug #20675180)

The Performance Schema threads table now contains a THREAD_OS_ID column that indicates the thread or task identifier as defined by the underlying operating system. For example, the column value corresponds to the Process Explorer thread ID on Windows and the gettid() value on Linux. For more information, see The threads Table.

If you upgrade to this MySQL release from an earlier version, you must run mysql_upgrade (and restart the server) to incorporate this change into the performance_schema database.

The audit plugin API has been extensively revised to support a finer breakdown of the general event type (MYSQL_AUDIT_GENERAL_CLASS) into more specific events. This enables audit plugins to more precisely indicate the types of events in which they are interested and reduces overhead for plugins that have use for only a few event types. The API also now permits early termination of event execution. For more information, see Writing Audit Plugins. The general event type is still available but is deprecated and will be removed in a future MySQL release.

In addition, a security_context plugin service is now available. Audit plugins can use this service to examine or modify the security context of threads associated with audited events. See MySQL Services for Plugins.

For RPM-based packages, the permissions used to create the data directory (/var/lib/mysql) have been changed from 755 to 751. This tightens the data directory permissions while still permitting world access to the mysql.sock file in that directory. (Bug #21066592)

The required version of the Boost library for server builds has been raised from 1.58.0 to 1.59.0. (Bug #77960, Bug #21567456)

Spatial functions such as ST_MPointFromText() and ST_GeomFromText() that accept WKT-format representations of MultiPoint values now permit individual points within values to be surrounded by parentheses. For example, both of the following function calls are valid, whereas previously the second one produced an error:

ST_MPointFromText('MULTIPOINT (1 1, 2 2, 3 3)')
ST_MPointFromText('MULTIPOINT ((1 1), (2 2), (3 3))')

In addition, functions such as ST_AsText() and ST_AsWKT() that produce WKT-format results now display MultiPoint values with parentheses surrounding each point. (Bug #54065, Bug #11761559)

The sys schema included in MySQL distributions was updated to version 1.5.0. This version includes new features:

sys schema 1.5.0 also includes fixes for several issues:

If you upgrade to this MySQL release from an earlier version, you must run mysql_upgrade to incorporate these changes into the sys schema.

Thanks to Daniël van Eeden, Jesper Wisborg Krogh, Shlomi Noach, and Morgan Tocker for their contributions to this update. (Bug #78115, Bug #21647101, Bug #77927, Bug #21550271, Bug #78720, Bug #21966366)

Incompatible Change; InnoDB: To better manage redo log format changes, the redo log header of the first redo log file (ib_logfile0) now includes a format version identifier and a text string that identifies the MySQL version that created the redo log files.

A new boolean configuration option, innodb_log_checksums, replaces the innodb_log_checksum_algorithm option. innodb_log_checksums=ON enables a CRC-32C checksum, making it the only supported checksum for redo log pages.

This patch also removes unused fields from the redo log header and checkpoint pages.

Due to redo log format changes introduced by this patch, upgrading to or downgrading from MySQL 5.7.9 and higher requires a clean shutdown and, in some cases, removal of existing redo log files. For instructions related to this change, see Changes Affecting Upgrades to MySQL 5.7, and Changes Affecting Downgrades from MySQL 5.7. (Bug #21759424, Bug #78275, Bug #21752674)

Important Change; InnoDB: DYNAMIC replaces COMPACT as the implicit default row format for InnoDB tables. A new configuration option, innodb_default_row_format, specifies the default InnoDB row format. Permitted values include DYNAMIC (the default), COMPACT, and REDUNDANT.

The COMPACT row format remained the default row format until this release to ensure compatibility with older versions of InnoDB in MySQL 5.1 and earlier. Now that MySQL 5.1 has reached the end of its product lifecycle, the newer DYNAMIC row format becomes the default. For information about advantages of the DYNAMIC row format, see DYNAMIC and COMPRESSED Row Formats.

Newly created tables use the row format defined by innodb_default_row_format when a ROW_FORMAT option is not specified explicitly or when ROW_FORMAT=DEFAULT is used.

Existing tables retain their current row format if a ROW_FORMAT option was specified explicitly. If a ROW_FORMAT option was not specified explicitly or if ROW_FORMAT=DEFAULT was used, any operation that rebuilds a table also silently changes the row format of the table to the format defined by innodb_default_row_format. For more information, see Specifying the Row Format for a Table.

Important Change: Introduced the -> JSON column-path operator. column->path is now supported as a synonym of JSON_EXTRACT(column, path), where column is a JSON column, and path is a valid JSON path.

An expression with ->, like its equivalent that uses JSON_EXTRACT() instead, can be used in place of a column identifier wherever the latter can occur within a valid SQL statement. For example, the following CREATE TABLE and SELECT statements are valid:

CREATE TABLE t1 (
  a JSON,
  b INT,
  g INT GENERATED ALWAYS AS (a->"$.id"),
  h INT GENERATED ALWAYS AS (a->"$.storeid"),
  INDEX i (g),
  INDEX j (h)
);

SELECT
  CONCAT(a->"$.fname", ' ', a->"$.lname") AS name,
  a->"$.id" AS id,
  a->"$.storeid" AS store
  FROM t1
  WHERE g > 500
  ORDER BY a->"$.storeid", a->"$.lname";

A column-path expression can be used for any column value that is read in a SELECT column list, or in a WHERE, ORDER BY, or GROUP BY clause in any SQL statement; such expressions cannot be used to set values.

When an SQL statement contains one or more expressions using -> notation, each of these is translated into an equivalent expression that employs the JSON_EXTRACT() function instead. This can be seen in the output from EXPLAIN when used on such a statement.

Like JSON_EXTRACT(), the -> operator returns as NULL if no matching value for an otherwise valid path is found.

For more information about -> and JSON_EXTRACT(), see Functions That Search JSON Values. See Searching and Modifying JSON Values, for information about JSON path support. See also Indexing a Generated Column to Provide a JSON Column Index, for additional information and examples.

InnoDB: A new INNODB_METRICS server operations counter (innodb_dict_lru_count) counts the number of tables evicted from the table cache LRU list. Thanks to Daniël van Eeden for the patch. (Bug #21682332, Bug #78190)

InnoDB: The new innodb_numa_interleave read-only configuration option allows you to enable the NUMA interleave memory policy for allocation of the InnoDB buffer pool. When innodb_numa_interleave is enabled, the NUMA memory policy is set to MPOL_INTERLEAVE for the mysqld process. After the InnoDB buffer pool is allocated, the NUMA memory policy is set back to MPOL_DEFAULT. This option is only available on NUMA-enabled systems.

Thanks to Stewart Smith for the patch. (Bug #18871046, Bug #72811)

MySQL distributions now include these header files because my_sys.h depends on them: my_thread_local.h, thr_cond.h, thr_mutex.h, thr_rwlock.h. (Bug #21909332)

MySQL Server RPM packages now obsolete MySQL Connector C. Installing MySQL Server causes older libmysqlclient from any MySQL Connector C packages to be removed and replaces them with the current libmysqlclient. (Bug #21900800)

RPM .spec files were updated so that MySQL Server builds from source RPM packages will include the proper files to take advantage of operating system NUMA capabilities. This introduces a runtime dependency on libnuma.so.1. RPM and yum detect this and refuse to install if that library is not installed. (Bug #21775221)

The JSON_APPEND() function was renamed to JSON_ARRAY_APPEND(). (Bug #21560934)

The server now generates a warning when the default_storage_engine or default_tmp_storage_engine system variable is set to a disabled storage engine named in the disabled_storage_engines system variable. (Bug #21405865)

Metadata locking for tablespaces has been extended so that, for DDL statements that refer to multiple tablespaces, a metadata lock is acquired on all used tablespaces. (Bug #21376265)

Unit testing now uses Google Mock 1.7 rather than 1.6. (Bug #21215389)

Support for building with Solaris Studio 5.13 was added. (Bug #21185883)

mysql_ssl_rsa_setup now is less noisy by default. Output from openssl commands is displayed only if --verbose is given. (Bug #21024979)

yaSSL was upgraded to version 2.3.8.

Upgrading from older versions fixes a connection-failure issue when used with the thread pool plugin. (Bug #20774956, Bug #21888925)

Insert overhead for the MEMORY storage table was reduced by caching computed hash values. (Bug #78480, Bug #21866029)

The initial-password message written by mysqld --initialize to the error log has been reduced from a [Warning] to a [Note]. (Bug #78182, Bug #21680457)

mysqlpump now supports a --version option. (Bug #77894, Bug #21534277)

Unneeded scripts and test files were removed from the tests directory and that directory was renamed to testclients. (Bug #77807, Bug #21490075)

The JSON value-updating functions JSON_APPEND(), JSON_SET(), JSON_REPLACE(), and JSON_INSERT() now treat SQL NULL values as JSON null literals, which is consistent with JSON_OBJECT() and JSON_ARRAY(). (Bug #77733, Bug #21450922)

Performance Schema digests in DIGEST_TEXT columns have ... appended to the end to indicate when statements exceed the maximum statement size and were truncated. This is also now done for statement text values in SQL_TEXT columns. (Bug #75861, Bug #20519832)

Output from mysql_upgrade is now less noisy and more informative. (Bug #59077, Bug #11766046)

A new SHUTDOWN SQL statement is available. This provides an SQL-level interface to the same functionality previously available using the mysqladmin shutdown command or the mysql_shutdown() C API function. See SHUTDOWN Syntax.

The mysql_shutdown() function and corresponding COM_SHUTDOWN client/server protocol command are deprecated and will be removed in a future version of MySQL. Instead, use mysql_query() to execute a SHUTDOWN statement.

Work was done to clean up the source code base, including: Removal of unneeded CMake checks; removing unused macros from source files; reorganizing header files to reduce the number of dependencies and make them more modular, removal of function declarations without definitions.

Important Change; InnoDB; Partitioning: There was no way to upgrade existing partitioned tables to use the native partitioning implemented for InnoDB tables in MySQL 5.7.6. This fix adds support to both mysql_upgrade and the mysql client for upgrading partitioned InnoDB tables created in previous releases, which used the ha_partition handler, to use InnoDB native partitioning instead.

(Bug #20727344, Bug #76374)

Important Change; Replication: The START SLAVE and STOP SLAVE statements can no longer be used for the group_replication_recovery channel. See Replication Channels, for more information. (Bug #21680074)

Important Change; Replication: In MySQL 5.7, the binlog_max_flush_queue_time system variable introduced in MySQL 5.6 no longer has any effect. This variable is now deprecated, and has been marked for eventual removal in a future MySQL release. (Bug #21347087)

Important Change; Replication: When using a single-threaded slave, the status of the applier thread is now reported as part of the replication_applier_status_by_worker table, instead of replication_applier_status_by_coordinator. This means that replication_applier_status_by_coordinator is now empty when using a single-threaded slave; it should be noted that such reporting for multi-threaded slaves has not been changed, and continues to be shown in that table. (Bug #74765, Bug #20001173)

InnoDB: The undo log contained insufficient information about virtual columns and virtual column indexes, which could cause a server exit when adding or dropping virtual columns. As a result, a slow shutdown (using innodb_fast_shutdown=0) is required prior to performing an in-place upgrade or downgrade from MySQL 5.7.8. For more information, refer to Upgrading or Downgrading MySQL. (Bug #21869656, Bug #78489)

InnoDB: A table-rebuilding ALTER TABLE operation that created an index on a virtual column raised an assertion. (Bug #21847170, Bug #78452)

InnoDB: A SELECT ... FOR UPDATE operation on a table with virtual generated columns raised an assertion. InnoDB unnecessarily retrieved a non-indexed virtual column for a covered secondary index scan. (Bug #21827963)

InnoDB: Creating a table with large rows failed when using a ROW_FORMAT=DYNAMIC or ROW_FORMAT=COMPRESSED due to an incorrect undo log record size calculation. The same operation succeeded with ROW_FORMAT=COMPACT or ROW_FORMAT=REDUNDANT.

ROW_FORMAT=DYNAMIC and ROW_FORMAT=COMPRESSED now permit a row length violation at DDL time if innodb_strict_mode is disabled. (Bug #21816041, Bug #78392)

InnoDB: Adding an index on a generated virtual column with an index prefix length that exceeded the maximum length caused a server exit. (Bug #21812026)

InnoDB: A memory leak occurred after crash recovery. Memory allocated in fil_space_read_name_and_filepath() was not freed. (Bug #21811321)

InnoDB: Altering the data type or computation method of a virtual generated column caused an error. (Bug #21810004)

InnoDB: An assertion was raised when creating a spatial index. InnoDB failed to count virtual columns that preceded the spatial index column. (Bug #21807340)

InnoDB: Tablespace discovery modifications in MySQL 5.7.5 included the removal of code related to MLOG_FILE_CREATE2 redo log records. As a result, the redo log did not contain sufficient information about file creation. (Bug #21801423, Bug #78363)

InnoDB: The redo log provided no indication that redo logging is disabled for index page writes during concurrent DDL operations. As a result, external hot backup tools could produce corrupt backups. (Bug #21796691, Bug #78351)

InnoDB: In debug builds, recovery asserted during a transparent page compression test. A torn page from the doublewrite buffer caused an LSN debug check failure. (Bug #21796092)

InnoDB: Creating a virtual generated column on a partitioned table caused a server exit. (Bug #21790751, Bug #78326)

InnoDB: An old version of numactl headers on the build host caused a compilation error when building a MySQL version that includes NUMA memory policy support. (Bug #21785074)

InnoDB: A SELECT .. FOR UPDATE operation on an indexed virtual generated column raised an assertion. (Bug #21775459)

InnoDB: The tablespace identifier (space_id) was logged twice for an MLOG_TRUNCATE redo log record. (Bug #21744589)

InnoDB: Crash recovery issued an invalid error message indicating that an isl file could not be opened or is not correct. (Bug #21691438)

InnoDB: The InnoDB Monitor displayed incorrect mutex creation information for a mutex with a long semaphore wait. (Bug #21682997, Bug #78179)

InnoDB: Error message formatting was corrected in the os_file_write_page() function. (Bug #21681433, Bug #78184)

InnoDB: The i_s_dict_fill_sys_tablespaces() function could free memory associated with a file name before printing an error message. (Bug #21680518, Bug #78180)

InnoDB: In debug builds, scanned and applied redo log records are now printed with a string identifier instead of a numerical identifier when --debug=d,ib_log is passed to mysqld. For example, rec MLOG_2BYTES is now printed instead of rec 2. (Bug #21664268, Bug #78148)

InnoDB: The number of system calls made by the InnoDB page compression feature was reduced. (Bug #21654695)

InnoDB: The recv_parse_log_rec function returned the length of the redo log record instead of 0 when encountering an incomplete MLOG_CHECKPOINT record. (Bug #21640085, Bug #78058)

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

InnoDB: In debug builds, a parenthesis mismatch in a MATCH() ... AGAINST clause raised a full-text parser assertion. (Bug #21638907)

InnoDB: Debug code was added to avoid a doublewrite buffer assertion that was raised during Valgrind testing. (Bug #21631197)

InnoDB: Log messages were improved to help identify out-of-space errors that could occur when adding rollback segments. (Bug #21629618)

InnoDB: In debug builds, enabling the innodb_log_checkpoint_now debug option while a table-rebuilding ALTER TABLE operation is running could result in an infinite loop. (Bug #21628087, Bug #78056)

InnoDB: UNIV_INLINE was not defined for the dict_table_has_indexed_v_cols function. (Bug #21628058, Bug #78055)

InnoDB: Altering a virtual column data type is not supported as an in-place operation. (Bug #21617377)

InnoDB: Sorting was skipped by an ALTER TABLE statement that changed the primary key and dropped the last column of the previous primary key. (Bug #21612714, Bug #78020)

InnoDB: During recovery, an invalid isl file was treated as a missing isl file, resulting in the tablespace being opened using the file location defined in an MLOG_FILE_* record in the redo log. Recovery no longer opens the tablespace if the isl file is invalid. (Bug #21577278, Bug #77986)

InnoDB: Code that provided a timeout mechanism intended to reduce adaptive hash index search latch (btr_search_latch) contention was removed. The code became obsolete after the introduction of adaptive hash index search system partitioning in MySQL 5.7.8. (Bug #21569876, Bug #77957)

InnoDB: The COMPRESSION option was displayed incorrectly in SHOW CREATE TABLE output. (Bug #21557723, Bug #77940)

InnoDB: An innodb_data_file_path mismatch raised an assertion, as did initializing the database with a data file size that was too small for the specified page size. (Bug #21551464)

InnoDB: A check was added to prevent accessing full-text index tables that are in an inconsistent state. (Bug #21529012)

InnoDB: A schema mismatch error occurred when importing a tablespace that was altered by DROP INDEX operation on the source server. (Bug #21514135, Bug #77659)

InnoDB: Creating an index on a virtual generated column after adding a full-text index on a preceding column raised an assertion. (Bug #21478389)

InnoDB: For tables with a DYNAMIC or COMPRESSED row format, more data than necessary was undo logged for virtual columns. (Bug #21477535)

InnoDB: An INSERT operation raised a btr_search_enabled assertion. Assertion code was too restrictive. (Bug #21457373)

InnoDB: Reloading a table that was evicted while empty caused an AUTO_INCREMENT value to be reset. (Bug #21454472, Bug #77743)

InnoDB: A crash during a TRUNCATE TABLE operation caused the server to exit on startup. (Bug #21451922)

InnoDB: The .isl was not removed when dropping a general tablespace that was created outside of the MySQL data directory. (Bug #21446772, Bug #77724)

InnoDB: An inconsistent read occurred under the REPEATABLE READ transaction isolation level. Transactions that operated on the same row were removed from transaction ID list in the incorrect order. (Bug #21433768, Bug #77699)

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

InnoDB: Attempting to create a general tablespace data file on a Windows root drive caused an error. (Bug #21419888, Bug #77676)

InnoDB: After disabling the adaptive hash index feature, an adaptive hash index latch was unnecessarily obtained and released. (Bug #21407023)

InnoDB: An ALTER TABLE operation on a table with an index defined on a virtual column incorrectly modified the data of the virtual column. (Bug #21376546, Bug #77628)

InnoDB: A virtual column-related purge operation raised an assertion. (Bug #21374258)

InnoDB: On a partitioned table, creating an index on a generated column raised an assertion. (Bug #21372331)

InnoDB: Resizing the buffer pool online raised an assertion due to a memory full condition. (Bug #21348684, Bug #77564)

InnoDB: An ALTER TABLE ... IMPORT TABLESPACE operation with innodb_page_size=4K and ROW_FORMAT=DYNAMIC raised an assertion. (Bug #21341030, Bug #77540)

InnoDB: For spatial indexes, InnoDB unnecessarily stored a 3072-byte prefix in undo log records instead of just the maximum bounding rectangle (MBR). For columns with externally stored data, both the prefix and MBR are logged. (Bug #21340268, Bug #77537)

InnoDB: Invalid init_ftfuncs() assertion code was removed. (Bug #21300774)

InnoDB: Memory allocation sanity checks were added to the memcached code. (Bug #21288106)

InnoDB: An incorrect reference count caused a hang in the TrxInInnoDB constructor. innobase_close_connection() released the transaction object before destroying the TrxInInnoDB object where the reference count is adjusted. (Bug #21280816)

InnoDB: A MySQL 5.7.8 patch that reintroduced SHOW ENGINE INNODB MUTEX functionality caused a performance regression. (Bug #21266784)

References: See also: Bug #77314, Bug #21238953.

InnoDB: A memcached flush_all command raised an assertion. A function that starts a transaction was called from within assertion code. (Bug #21239299, Bug #75199)

InnoDB: A shutdown hang occurred when a high priority transaction waited for a victim transaction to exit while the victim transaction waited for an asynchronous rollback to complete. (Bug #21143276)

InnoDB: A data corruption occurred on ARM64. GCC builtins did not issue the correct fences when setting or unsetting the lock word. (Bug #21102971, Bug #76135)

InnoDB: Server shutdown was delayed waiting for the purge thread to exit. To avoid this problem, the number of calls to trx_purge() was reduced, and the trx_purge() batch size was reduced to 20. (Bug #21040050)

InnoDB: In READ COMMITTED mode, a REPLACE operation on a unique secondary index resulted in a constraint violation. Thanks to Alexey Kopytov for the patch. (Bug #21025880, Bug #76927)

InnoDB: The IBUF_BITMAP_FREE bit indicated that there was more free space in the leaf page than was actually available. (Bug #20796566)

InnoDB: Moving the data directory before recovering a crashed database caused tablespace discovery to fail for file-per-table tablespaces created outside of the MySQL data directory. (Bug #20698468, Bug #76308)

InnoDB: The innodb_buf_flush_list_now debug setting failed to flush all dirty pages to disk. (Bug #20582189)

InnoDB: An ALTER TABLE ... ADD FULLTEXT INDEX operation raised an assertion. A thread attempted to use a lower priority transaction that was being rolled back before the rollback operation completed. (Bug #20481175)

InnoDB: Running an ALTER TABLE operation on a referencing table with a cascading foreign key constraint during a concurrent DML operation on the referenced table caused a loss of referential integrity. (Bug #20367116)

InnoDB: Setting lower_case_table_names=0 on a case-insensitive file system could result in a hang condition when running an INSERT INTO ... SELECT ... FROM tbl_name operation with the wrong tbl_name letter case. An error message is now printed and the server exits when attempting to start the server with --lower_case_table_names=0 on a case-insensitive file system. (Bug #20198490, Bug #75185)

InnoDB: The server failed to start with an innodb_force_recovery setting greater than 3. InnoDB was set to read-only mode before redo logs were applied.

DROP TABLE is now supported with an innodb_force_recovery setting greater than 3. (Bug #19779113)

InnoDB: The trx_sys_read_pertable_file_format_id() function reported the wrong file format. (Bug #19206671)

InnoDB: The mysql_system_tables_fix_for_downgrade.sql script, provided to facilitate system table alterations when downgrading from MySQL 5.7.6 or higher, was removed from the MySQL installation directory. The script was no longer valid for all downgrade paths. For more information, see Changes Affecting Downgrades from MySQL 5.7. (Bug #78259, Bug #21753832)

InnoDB: A virtual generated column on a table that uses index condition pushdown (ICP) caused an assertion. (Bug #77842, Bug #21507796, Bug #21478287)

Packaging; OS X: Using user=mysql during installation on OS X did not allow the mysql database to be installed. To fix this problem, OS X packages now use the --no-defaults option when creating this database. This also means that having a my.cnf file on the system no longer affects the installation. (Bug #21364902)

Partitioning: Error handling for failed partitioning-related ALTER TABLE operations against non-partitioned tables was not performed correctly (Bug #20284744)

Partitioning: ALTER TABLE when executed from a stored procedure did not always work correctly with tables partitioned by RANGE. (Bug #77333, Bug #16613004, Bug #21246891)

Replication: The group replication applier channel does not support DATABASE as the slave_parallel_type; when group replication is started, this is checked for explicitly, and handled correctly. However, it remained possible to change this value indirectly at a later point in time by increasing the value of slave_parallel_workers while the slave SQL thread was stopped, which caused the applier to fail with an error. To fix this problem, the slave_parallel_type for the group_replication_applier is now checked to make sure that it is set to LOGICAL_CLOCK whenever the number of slave_parallel_workers is set greater then 0, and not merely when group replication is first started. (Bug #21798804)

Replication: As binlog_error_action=ABORT_SERVER is the default in MySQL 5.7.7 and later it is being used for more error situations. The behavior has been adjusted to generate a core dump to improve troubleshooting possibilities. (Bug #21486161, Bug #77738)

Replication: At runtime, some Gtid_set objects could be instrumented with a performance schema mutex key equal to 0 (which is invalid), due to its use as the effective default value when the mutex key was not actually supplied. This allowed these objects to be created without a valid key, which led to further issues when using them. (Bug #21485997)

Replication: When running the server with gtid_mode=ON, a DELETE from a MEMORY table following a restart was not written to the binary log correctly. (Bug #21045848)

Replication: The locking behavior of replication administration statements has changed to make SHOW SLAVE STATUS more concurrent. This makes the NONBLOCKING clause redundant for SHOW SLAVE STATUS and it has been removed. (Bug #20593028)

Replication: ER_CANT_USE_AUTO_POSITION_WITH_GTID_MODE_OFF errors were not reported using the correct format. (Bug #20545943)

Replication: When the dump thread was killed while dumping an inactive binary log, some events in this log could be skipped and thus not replicated. (Bug #78337, Bug #21816399)

References: See also: Bug #74607, Bug #19975697.

Replication: XA transactions could cause an assert condition on XA COMMIT; this was happening because the internal transaction state was not reset between XA PREPARE and XA COMMIT or XA ROLLBACK, due to the fact that these operations constitute separate transactions under XA. In addition, XA ROLLBACK statements were not handled properly in some cases. (Bug #78264, Bug #21755890)

Replication: The interface between the Group Replication plugin and the Performance Schema engine made use of a type of memory allocation which was passed to the server, and was a potential source of problems when passing information between the plugin and performance_schema tables. The implementation for this interface has been reworked so as to avoid performing this type of memory allocation when sharing data. (Bug #78263, Bug #21755699)

Replication: The MTS submode set for each channel was ignored by the worker threads, which continued to read and use the global flag set for all slave channels. This could lead to errors when the coordinator was of one type and its workers of another. (Bug #77763, Bug #21464737)

Replication: Replication slaves could fail for having insufficient privileges when they had been granted only the REPLICATION SLAVE privilege. (Bug #77732, Bug #21455603)

Replication: The status variable Slave_open_temp_tables keeps track of the number of temporary tables that are opened by the replication slave. If multi-source replication is enabled, it is the total number of temporary tables for all channels. This fix addresses the following issues relating to this variable:

(Bug #77585, Bug #21357008)

Replication: The warning '@@session.gtid_executed' is deprecated and will be removed in a future release. was printed even when the session variable gtid_executed was not included in the result of a query. In addition, the result of SELECT @@session.gtid_executed included a duplicate warning. Both issues occurred because the warning was printed whenever the value of gtid_executed was accessed by a statement, such access occurring as a matter of course, whether or not a given variable is actually included in the result.

To fix this issue, we make handling of @@session.gtid_executed consistent with how the also-deprecated variable @@global.sql_log_bin is treated in such cases, by making the following changes:

The warning is still issued by a statement such as SELECT @@session.gtid_executed which accesses the value of the variable directly. (Bug #77574, Bug #21354712)

References: See also: Bug #75980, Bug #20575529, Bug #76626, Bug #20854952.

Replication: When a transaction consisting of a single statement with a specified GTID failed in autocommit mode, its GTID was not released when rolling it back when binary logging was disabled. (Bug #77521, Bug #21338147)

Replication: The slave group event parser did not properly register an XA_ROLLBACK event as a transaction boundary. (Bug #77392, Bug #21273010)

References: See also: Bug #20920851.

Replication: mysqlbinlog printed a ROLLBACK statement at the end of the binary log file, which when played back failed with error 1782 @@SESSION.GTID_NEXT cannot be set to ANONYMOUS when @@GLOBAL.GTID_MODE = ON. This occurred when the binary log file did not include any data related events, or when the relay log file included a Format_description_log_event that had been generated on the master at server startup.

The fix for this issue causes a relay log's Format_description_log_event to do nothing if it is applied by a BINLOG statement, and stops a ROLLBACK from setting gtid_next to ANONYMOUS when the state of gtid_next has not yet been determined by a subsequent event. (Bug #76887, Bug #20980932)

Replication: SAVEPOINT and ROLLBACK TO SAVEPOINT within a trigger led to an assertion. (Bug #76727, Bug #20901025)

Replication: While a SHOW BINLOG EVENTS statement was executing, any parallel transaction was blocked. The fix ensures that the SHOW BINLOG EVENTS process now only acquires a lock for the duration of calculating the file's end position, therefore parallel transactions are not blocked for long durations. (Bug #76618, Bug #20928790)

Replication: If a CREATE VIEW statement failed, it was being incorrectly written to the binary log even though it did not result in the creation of a partial view. The fix ensures that such statements are not recorded in the binary log. Additionally it was found that when a statement which had failed on a master was received by a slave with an expected error, if the statement was skipped on the slave, for example due to a replication filter, the expected error was being compared with the actual error that happened on the slave. The fix ensures that if a statement with an expected error is received by a slave, if the statement has not been filtered, only then is it compared with the actual error that happened on the slave. (Bug #76493, Bug #20797764)

Replication: The action specified for binlog_error_action was not always honored correctly after a hardware failure occurred during log rotation. (Bug #76379, Bug #20805298)

Replication: When using MySQL 5.7.6 and later with binlog_format=row and gtid_mode=off, if CREATE ... SELECT was killed during execution it could lead to an inconsistent state, breaking replication. The cause was that in MySQL 5.7.6 the way CREATE ... SELECT was logged was changed, so that a commit was introduced between the CREATE TABLE and SELECT steps. The fix ensures that CREATE ... SELECT does not commit in the middle of the transaction when binlog_format=row. (Bug #76320, Bug #77098, Bug #20742519, Bug #21114464)

Replication: Modifying the master_info_repository or relay_log_info_repository inside a transaction and later rolling back that transaction left the repository in an unusable state. We fix this by preventing any modification of these repositories inside a transaction. (Bug #74950, Bug #20074353)

Replication: Transactions added to gtid_executed using SET gtid_purged were not taken into account by WAIT_FOR_EXECUTED_GTID_SET() until a subsequent transaction was committed by a client or slave thread. (Bug #73838, Bug #19579811)

Replication: When using --relay-log-info-repository=TABLE, the mysql.slave_relay_log_info table is updated when a transaction is committed or when a flush is performed explicitly, such as during relay log rotation. If a transaction that uses any nontransactional tables (for example MyISAM tables) is split across multiple relay logs, it is partially committed on relay log flush. When gtid_mode=ON, this caused the same GTID to be used for the remaining portion of the transaction, which raised an ER_GTID_NEXT_TYPE_UNDEFINED_GROUP error.

We fix this issue by postponing in such cases the update of the relay log information repository that normally occurs on relay log rotation until the commit for the transaction in question has been executed.

This issue did not affect tables using transactional storage engines such as InnoDB. (Bug #68525, Bug #16418100)

References: See also: Bug #21630907, Bug #76974.

RHEL RPM packages had incorrect dependency information. (Bug #22218841)

For an index-only scan over an indexed generated column, the server could do random calculations; the random results were not exposed to the user, but Valgrind warnings could occur, and the server could exit when calculations involved functions which did not expect such incorrect data. (Bug #21833760)

Although the use of JSON values with GREATEST() or LEAST() is not currently supported, the server did not handle attempts to do so correctly, leading to an assert (Linux) or exit() call (Windows) in debug builds. Now when you try to use JSON values with either of these functions, the server emits a suitable warning (ER_NOT_SUPPORTED_YET). (Bug #21828321)

References: See also: Bug #21383497.

A table that included a generated column referencing a JSON column in some cases become corrupted, so that a subsequent access of the table using a different connection caused the server to fail. (Bug #21808680)

References: See also: Bug #21824519, Bug #78408.

For tables with VIRTUAL generated columns, an INSERT with an empty values list could cause a server exit. (Bug #21807818)

CMake configuration was adjusted to handle new warnings reported by Clang 3.7. (Bug #21803314)

For plugins of type PROTOCOL_PLUGIN, execution of INSTALL PLUGIN, UNINSTALL PLUGIN, or SHUTDOWN could cause a server exit. Such plugins are no longer permitted to execute these statements. (Bug #21797816)

Using a materialized view defined over a table containing generated columns could cause a server exit. (Bug #21797776)

For partitioned InnoDB tables containing a virtual generated column, reads from the table could return random data for the column. (Bug #21779011)

The CMake checks for NUMA availability could cause compilation problems on platforms without NUMA support. (Bug #21774859)

The optimizer did not consider nonfunctional expressions such as (a AND b) = 1 when looking for indexed generated columns to substitute for the (a AND b) expression. Now expressions using the AND and OR logical operators are considered. (Bug #21770798)

For debug builds, when the optimizer tried to clone certain types of keys for a range optimization, an assertion was raised. (Bug #21761867)

For debug builds, the server could exit when the optimizer attempted to estimate the cost for processing unique values when there were no keys. (Bug #21697002)

An INSERT into a view with a subquery could fail if executed as a prepared statement. (Bug #21696206)

For queries on InnoDB tables for which the optimizer used SPATIAL indexes for full index scans, the result was empty because such indexes do not support a full scan. The optimizer no longer considers SPATIAL indexes as candidates for full index scans. (Bug #21663612)

For some inputs, ST_Intersection() could return an invalid polygon. (Bug #21658453)

Spatial functions could simplify geometry values in contexts where the value might be used elsewhere in a query, producing incorrect results. (Bug #21652012)

If ST_ConvexHull() or ST_SRID() were used in a view definition, the resulting definition contained ST_Convex_Hull() (misspelled) or SRID() (deprecated). (Bug #21651588)

JSON_TYPE() returned OPAQUE for some binary values that it should have identified as BLOB. (Bug #21649073)

For debug builds, enabling the PAD_CHAR_TO_FULL_LENGTH SQL mode could cause SHOW FUNCTION STATUS to raise an assertion. (Bug #21632425)

mysqlpump did not exit with a message for some combinations of incompatible options. (Bug #21628662)

An assertion could be raised if the optimizer tried to create a temporary table based on a prepared statement parameter. (Bug #21625929)

Executing a prepared statement with multiple nested subqueries could raise an assertion. (Bug #21624851)

For debug builds, failure of subquery optimization could cause an assertion to be raised due to improper error handling. (Bug #21621313)

Some table and index optimizer hints were lost early in statement processing, so query rewrite plugins did not have access to them. This could cause incorrect matching between incoming statements and statement pattern templates. (Bug #21619780)

Queries containing nested subqueries combining grouping and outer references might cause a server exit. (Bug #21619634)

Passing NULL as the second or third argument to ST_AsGeoJSON() could cause the server to stop responding to the session or (in debug builds) to raise an assertion.

Giving input to HANDLER READ that could not be converted to the correct type could cause the server to stop responding to the session or (in debug builds) to raise an assertion. (Bug #21616810, Bug #21650603)

For debug builds, ST_IsValid(NULL) could raise an assertion. (Bug #21616647)

For debug builds, an assertion could be raised for negative zero values when converting time values to decimal. (Bug #21616585)

ST_AsWKB() could cause a server exit if given invalid data. (Bug #21614368)

References: See also: Bug #22131961.

If an aggregate function was used over a generated column that was itself part of a multiple-column index, the server could exit. (Bug #21613615)

A missing error check during column reference resolution could result in an incorrect error message or (in debug builds) an assertion being raised. (Bug #21613422)

For debug builds, an assertion could be raised in Filesort::make_sortorder() for attempts to sort Item_ref objects. (Bug #21611270)

JSON functions could return incorrect values if a path argument was passed as a user-defined variable that changed values between result set rows. (Bug #21602361)

For debug builds, an assertion was raised for some queries that have a semi-join and use the materialization strategy, if a key length or number of key parts was zero. (Bug #21566735)

Compilation using gcc 4.9 or 5.1 failed on ARM64 platforms. (Bug #21552524)

References: See also: Bug #21845828.

If a multiple-column UPDATE statement failed to update a JSON column that was then referenced in a later update, the server could exit. (Bug #21547877)

For debug builds, invalid geometry byte strings could cause spatial functions to raise an assertion rather than return an error to the caller. (Bug #21546656)

For debug builds, a too-strict assertion could be raised by invalid characters for LOAD DATA. (Bug #21542698)

The server could exit when InnoDB tried to update a secondary index on a VIRTUAL generated column of type BLOB. (Bug #21530366)

For debug builds, incorrect caching of JSON values could cause an assertion to be raised. (Bug #21491442)

An empty string (which is not a valid JSON value) normally is parsed and returned as a JSON null literal, but in some cases could raise an assertion for debug builds. (Bug #21487833)

For temporary tables created to handle UNION statements that selected CHAR or SET columns, the maximum column width could be too long for InnoDB to handle. Now such columns are created as variable-length columns. (Bug #21480999)

For builds configured with MAX_INDEXES greater than 64, certain queries for which the server used temporary tables could cause a server exit. (Bug #21466850)

Adding or dropping a VIRTUAL generated column could cause a server exit. (Bug #21465626)

For plugins that use the audit plugin API, MYSQL_AUDIT_GLOBAL_VARIABLE_SET events passed to the notification function did not include the new variable value. (Bug #21457699)

Queries on a table containing an indexed generated column could fail if the table name contained special characters. (Bug #21454155)

When a view was the inner table of an outer join, a JSON column could produce a non-NULL value when NULL was expected. (Bug #21448719)

If JSON_CONTAINS_PATH() was called with a one_or_all argument of all and a path argument contained a wildcard, the function found all matches per path, even though in this case one match is sufficient. (Bug #21442775)

JSON_SET() and JSON_REPLACE() sometimes produced an incorrect result if a path expression identified a nonarray value. (Bug #21442624)

Suppression of JSON conversion errors using non-strict SQL mode or INSERT IGNORE could then cause an assertion to be raised if an empty value inserted into a JSON NOT NULL column was copied to another JSON column. (Bug #21437989)

For debug builds, some spatial functions that accept raw byte data for spatial arguments (for example, specified as hex values) could raise an assertion if such an argument contained extra garbage following valid data. (Bug #21397107)

For deeply nested JSON input, ST_GeomFromGeoJSON() or JSON_VALID() could produce stack overflow. (Bug #21389101, Bug #21377136)

Failure to parse a JSON string that contained a floating-point number with a large, negative exponent could cause a server exit. (Bug #21384048)

For debug builds, an incorrect assertion could be raised during subquery execution. (Bug #21383882)

For debug builds, a missing error check in Item_sum_hybrid::fix_fields() caused an assertion to be raised. (Bug #21383714)

For debug builds, invoking ST_AsGeoJSON() within GROUP BY ... WITH ROLLUP could raise an assertion. (Bug #21383497)

JSON_SEARCH() could return incorrect results if an invalid escape expression was specified. (Bug #21383284)

For debug builds, a NULL first argument to JSON_SET() could raise an assertion. (Bug #21381806)

For expressions of the form (subquery) IN (subquery), where a subquery could return a JSON value, failure to handle a row result could cause a server exit.` (Bug #21376088)

Failure of JSON_APPEND() to handle a legal condition could cause a server exit. (Bug #21373874)

Calls to ST_Buffer() could hang or raise an assertion. (Bug #21372946)

The server could exit in unclean fashion if configured to listen on a TCP/IP port number already in use by another server instance. (Bug #21368299)

Certain subqueries as arguments to PROCEDURE ANALYSE() could cause a server exit. (Bug #21350175)

A query with a right outer join inside a derived table might return wrong data. (Bug #21350125)

Starting the server with --skip-grant-tables (or with options such as --initialize for which --skip-grant-tables is implicit) prevented the INSTALL PLUGIN and UNINSTALL PLUGIN statements from working. (Bug #21335821)

mysql_ssl_rsa_setup could create an unwanted .rnd file in the data directory. (The file is actually created by openssl, which mysql_ssl_ras_setup invokes. mysql_ssl_rsa_setup now cleans up the file.) (Bug #21335818)

Some INFORMATION_SCHEMA queries consumed excessive memory due to suboptimal query plans and insufficient materialization. (Bug #21299665)

With the server configured to send error messages to syslog or a log file, messages generated prior to error log setup were sent to stderr or stdout. These messages are now buffered until error log setup has completed, then logged to the proper destination. (Bug #21296553)

Executing a prepared statement using a derived table and an aggregate function in a subquery in the SELECT list could cause a server exit. (Bug #21277074)

GRANT created the account for nonexistent accounts even if the NO_AUTO_CREATE_USER SQL mode was enabled. (Bug #21271571)

A query with a NOT IN subquery that had COUNT(DISTINCT) could return incorrect results. (Bug #21243772)

When started using a very old data directory (from MySQL 5.0), the server could exit due to failure to properly read the old grant tables. (Bug #21216433)

A mulitple-table update involving generated columns that updated used a temporary table could cause a server exit or raise an assertion. (Bug #21216067)

For queries containing an expression of the form (x IN (subquery)) IN (subquery2), a combination of semi-join and subquery materialization strategies could cause a server exit. (Bug #21205577)

If a query contained an outer join such as LEFT JOIN (t1,t2,...) and a hint was used to disable join buffering on a right-side table but not on the others, a server exit occurred. (Bug #21205282)

For a cursor type of CURSOR_TYPE_READ_ONLY, retrieving the result set for the first execution of a prepared CALL staement could be missing the first result set row if the data was numeric; raise an assertion for debug builds if the data was string; cause loss of the server connection when calling mysql_stmt_fetch(). (Bug #21199582)

Dangling blob pointers could remain when closing an InnoDB table, resulting in a subsequent read of invalid memory and a server exit. (Bug #21153489)

For some operations where sorting or grouping required a temporary table, the table could have zero columns and raise an assertion. (Bug #21143151)

Queries containing an expression of the form (x IS NULL) IN (subquery) could cause a server exit. (Bug #21139402)

During server SSL file autogeneration, ca.pem briefly had insecure file permissions. (Bug #21138119)

An assertion could be raised due to incorrect error handling if a SELECT ... FOR UPDATE subquery resulted in deadlock and caused a rollback. (Bug #21096444)

Selecting the result of an INSERT() function call to which input was passed as a hexidecimal string could expose more information than was passed to the function. (Bug #21056907)

Subqueries having COUNT() with GROUP BY could yield incorrect results. (Bug #21055139, Bug #78029, Bug #21615020)

The updatable property of a view is set during view creation. If the underlying table was dropped and re-created as a nonupdatable one, the updatable property of the original view was not revised accordingly. This could cause a server exit for attempts to insert or replace into the view is made. (This problem was specific to views with multiple tables/views and did not occur with update statements.) (Bug #21039264)

The locking functions provided by the version_token plugin were renamed: vtoken_get_read_locks(), vtoken_get_write_locks(), and vtoken_release_locks() are now named version_tokens_lock_shared(), version_tokens_lock_exclusive(), and version_tokens_unlock(), respectively.

These functions also failed to have any effect because they were implicitly unlocked at the end of the statement in which they were set. (Bug #21034322, Bug #21280801)

Servers linked against yaSSL and compiled with GCC 4.8.2 could fail to respond correctly to connection attempts until several seconds after startup. (Bug #21025377)

When upgrading an old data directory (MySQL 5.0 or 5.1), mysql_upgrade could fail to properly read the mysql.proc table. (Bug #20968596)

For tables with subpartitions, the server could exit due to incorrect error handling during partition pruning if the partition could be identified but not the subpartition. (Bug #20909518)

mysql_upgrade could fail to look for checked tables in the wrong database during the repair phase. (Bug #20868496)

DELETE could check privileges for the wrong database when table aliases were used. (Bug #20777016)

mysqldump used incorrect syntax for generated column definitions. (Bug #20769542)

Within a trigger, use of a cursor that accessed OLD or NEW values from a row could cause a server exit. (Bug #20760261)

Failure during execution of an XA PREPARE statement could result in an invalid XA transaction state. Subsequent attempts to start another XA transaction led to an ER_XAER_OUTSIDE error. (Bug #20538956)

The audit log plugin could audit accounts named in the audit_log_exclude_accounts system variable. (Bug #20408206)

If a generated foreign key index was renamed by the same ALTER TABLE statement that added a new foreign key with the same name, the server could exit. (Bug #20146455)

ALTER TABLE operations that dropped and added the same FULLTEXT index were not performed as in-place (fast) operations that avoid using a temporary copy of the table. (Bug #20106837)

When the number of days calculated by DATE_FORMAT() function was negative, the server could exit. (Bug #19985318)

ALTER TABLE operations to add or modify columns could create geometry columns containing invalid data due to missing validation. (Bug #19880316)

If range optimization was attempted on an index with a string column as its first part and values used for comparison were fully truncated, comparisons would be incorrect and produce incorrect results. (Bug #19333852)

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

The server could hang due to incorrect cleanup of aggregate functions used in a query. (Bug #18979515)

The server could exit while checking for appropriate indexes to use for certain queries that used aggregate function in the WHERE clause. (Bug #18706592)

On Windows, the validate_password plugin could cause a server exit during the dictionary check. (Bug #18636874)

Invoking a stored program without qualifying it with the database name could lead to stored program compilation errors. (Bug #18599181)

EXPLAIN of statements containing GROUP_CONCAT() could cause a server exit. (Bug #17865675)

The value of the FOUND_ROWS() function that returns the number of rows found in the previous query could change during execution of the next query. Now the value of FOUND_ROWS() for the previous query remains constant during execution of the next query. (Bug #17846246)

Failure to check for error conditions could cause some updates or deletes to result in a server exit. (Bug #17763238)

On Windows, heap corruption in the audit log plugin caused server startup failure. (Bug #14700102)

If the UPDATE part of INSERT ... ON DUPLICATE KEY UPDATE swapped two column values, the server could read incorrect data and exit. (Bug #13901905)

For debug builds, merging a derived table into an outer query block could raise an assertion. (Bug #79502, Bug #22305361, Bug #21139722)

mysqlpump failed to compile with Clang. (Bug #78637, Bug #21924096)

For debug builds, a DROP TRIGGER statement could raise an assertion if the trigger was defined on a table that contained a generated column. (Bug #78408, Bug #21824519)

Some stress test files in the mysql-test/suite/innodb_stress directory had the executable file mode set although they were not script files. (Bug #78403, Bug #21822413)

Subqueries that used a derived table and contained a set function referring to a column from that derived table might be aggregated in the wrong query block. (Bug #78250, Bug #21753180)

For some inputs, ST_Union() could return an invalid geometry collection. (Bug #78206, Bug #21689998)

On non-Windows systems, setting range_alloc_block_size or query_alloc_block_size to a value larger than 32 bits at startup could cause a server exit. The maximum value for these system variables (on all platforms) is now limited to 2³² − 1, rounded down to the nearest multiple of 1024. (Bug #78188, Bug #21682231)

mysql-test-run.pl now has an --valgrind-clients option that causes all clients started by .test files to be run with valgrind. This option requires valgrind 3.9 or later.

In addition, several client memory leak issues were fixed. (Bug #78165, Bug #21672747)

The mysql client parser incorrectly interpreted optimizer hint comments that contained ;, ", ', or ` characters. (Bug #78114, Bug #21646026)

These Version Tokens issues were resolved:

(Bug #78111, Bug #21645001, Bug #21646106, Bug #21645944, Bug #21646017)

Columns selected from the right-hand table of a left join, which was also a derived table, might produce incorrect NULL value information when used in an IN subquery. (Bug #77980, Bug #21574933)

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

On Windows, if the MySQL server was started as a service, logging to the error log file was disabled. (Bug #77977, Bug #21574096)

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

In the setup_instruments Performance Schema table, it was possible to set memory instrument to TIMED='YES', although memory operations are never timed. Now such attempts are ignored. It was possible to set built-in memory instruments (with names of the form memory/performance_schema/%) to ENABLED='YES', although built-in memory instruments cannot be disabled. Now such attempts are ignored. (Bug #77944, Bug #21562212)

mysqldump and mysqlpump output included sys schema stored programs even when the sys schema was not dumped. (Bug #77926, Bug #21549860)

RPM installation scripts failed if configuration files contained multiple datadir lines. Now the last datadir line is used. (Bug #77878, Bug #21527467)

An unnecessary memset() call invoked during Performance Schema digest operations has been removed, which improves performance by reducing overhead. (Bug #77863, Bug #21528683)

A potential race condition for the safe mutex implementation was corrected. This implementation is enabled by default only for debug builds. (Bug #77862, Bug #21522888)

Binary logging of CREATE USER and statements could log the hash of the password hash (rather than the hash itself) when log_backward_compatible_user_definitions was enabled. Binary logging of ALTER USER statements could include attributes not present in the original statements.

In consequence of the fix for these issues, log_backward_compatible_user_definitions has been replaced by log_builtin_as_identified_by_password. If this variable is enabled, binary logging for CREATE USER statements involving built-in authentication plugins rewrites the statements to include an IDENTIFIED BY PASSWORD clause, and SET PASSWORD statements are logged as SET PASSWORD statements, rather than being rewritten to ALTER USER statements. (Bug #77860, Bug #21516392, Bug #20535561)

mysqld --initialize produced warnings about missing SSL files, which is unnecessary because initialization does not require SSL. (Bug #77825, Bug #21498544)

Certain JSON functions could return incorrect results when used in prepared statements which had path expression constants. (Bug #77785, Bug #21472872)

Valgrind errors could occur during partition pruning for tables containing generated columns. (Bug #77782, Bug #21469535)

When mysqlpump was invoked with the --defer-table-indexes option, it could generate incorrect CREATE TABLE statements for tables with a foreign key and a primary key but not a secondary index. (Bug #77759, Bug #21462732)

An attempt to use a previously unused time zone with CONVERT_TZ() could produce warnings or errors or (in debug builds) raise an assertion if GTIDs were enabled but the binary log was not enabled.

In debug builds, an attempt to use a previously unused time zone with CONVERT_TZ() or as the value of the time_zone system variable inside a stored program could raise an assertion. (Bug #77753, Bug #21459999, Bug #77748, Bug #21459795)

The server initialization script used for the service mysql status command on Linux sometimes incorrectly reported that the server was stopped. (Bug #77696, Bug #21768876)

ALTER TABLE could raise an assertion for a table with an indexed virtual column having a column position greater than 64. (Bug #77656, Bug #21391781)

Evaluation of virtual generated columns could fail to evaluate all base columns and result in invalid memory reads. (Bug #77653, Bug #21390605)

For statements of the form CREATE TABLE ... SELECT, where the table was defined to contain a DECIMAL UNSIGNED, calculation of the row size was incorrect, leading to incorrect values in the table. (Bug #77636, Bug #21383896)

A WHERE predicate containing both TRIM(LEADING ..) and TRIM(TRAILING ...) could be incorrectly optimized away. (Bug #77631, Bug #21447969)

For wait events, the Performance Schema uses the CYCLE timer by default, but failed to fall back to a different timer if CYCLE was unavailable. (Bug #77577, Bug #21374104)

A disk-full condition during execution of a CREATE TABLESPACE statement caused a server exit. (Bug #77556, Bug #21347001)

A privilege precheck for derived tables could fail and cause a server exit. (Bug #77525, Bug #21338077)

For spatial functions, input polygons were automatically closed if open. However, the Open Geospatial Consortium guidelines require that input polygons already be closed. Unclosed polygons are now rejected as invalid rather than being closed. (Bug #77505, Bug #21327888)

When a VIRTUAL generated column was added to a table, it was not ensured that data being calculated by the generated column expression would not be out of range for the column. This could lead to inconsistent data being returned and unexpectedly failed statements.

ALTER TABLE now supports WITHOUT VALIDATION and WITH VALIDATION clauses to control whether ALTER TABLE validates the data for a VIRTUAL generated column:

WITHOUT VALIDATION and WITH VALIDATION are permitted only with ADD COLUMN, CHANGE COLUMN, and MODIFY COLUMN operations. (Bug #77478, Bug #21317507)

For some string functions, data was truncated when evaluated in subqueries due to incorrect space calculations when creating temporary tables to hold intermediate results. (Bug #77473, Bug #21317406)

Statement digests did not include information about optimizer hint comments, causing statements with and without hints to be aggregated. (Bug #77414, Bug #21286261)

A predicate of the form WHERE ROUND(X,Y) > 0, where X is a column name and Y is a program local variable, could return false when it should return true. (Bug #77391, Bug #21279005)

ST_SymDifference() with multipolygon arguments could return incorrect results. (Bug #77372, Bug #21263152)

Updating VARCHAR and TEXT columns in the same UPDATE statement could produce incorrect results. When a VARCHAR column was assigned to a TEXT column and the VARCHAR column was then set to a different value, the TEXT column's result contained the VARCHAR column's new value. (Bug #77135, Bug #21143080)

A subquery in a HAVING clause that returned more than 1 row could cause a server exit.

Additional to the bug fix, EXPLAIN now displays Zero limit rather than Impossible WHERE when optimizing a query with LIMIT 0. (Bug #76998, Bug #21067109)

If an INFORMATION_SCHEMA query that performed a table-open operation encountered a corrupt table and attempted to repair it, a deadlock could occur, resulting in an aborted transaction without an appropriate error being reported. Such queries now do not attempt table repair. (Bug #76912, Bug #21021848)

mysqladmin -u root -p could exit with a segmentation fault. (Bug #76538, Bug #20802751)

The optimizer sometimes generates an index for a derived table (subquery in the FROM clause). If this occurred for a statement executed within a stored program, a memory leak could occur. (Bug #76349, Bug #20728894)

Optimizer estimates for filtering conditions could lead to suboptimal execution plans if the expected number of rows selected from a table was between 0 and 1. The estimate is now made to be at least 1. (Bug #76314, Bug #20701585)

If a file was specified using an --init-file option, mysqld --initialize produced errors for statements in the file such as GRANT that affect user accounts. (Bug #75918, Bug #20546898)

The optimizer could incorrectly assume an out-of-memory condition while optimizing a range scan for the OR operator, resulting in overestimation of the number of qualifying rows. (Bug #75248, Bug #20229614)

The events_statements_history Performance Schema table could have an ERRORS column value of 0 when other columns indicated there were errors. (Bug #74614, Bug #19929832)

View creation from a UNION failed with a duplicate-column error if a SELECT statement in the UNION other than the first used the same column name multiple times. (Bug #74539, Bug #19886430)

Timestamp values written to the slow query log could be incorrect. (Bug #73974, Bug #19646918)

When the mysql client was used to connect to the server in batch mode using an account with an expired password, the error message was not meaningful. mysql now reports “Please use --connect-expired-password option or invoke mysql in interactive mode” in this case. (Bug #72696, Bug #21464621)

For UPDATE statements with ORDER BY, the optimizer could perform an unnecessary filesort on a key that was used for scanning as well as being updated. (Bug #72518, Bug #18698556)

For a query with many range conditions, the optimizer would estimate that too much memory would be required for a range scan and fall back to a less optimal plan, such as a full table scan.

A new range_optimizer_max_mem_size system variable now controls the limit on memory consumption for the range optimizer. A value of 0 means “no limit.” If an execution plan considered by the optimizer uses the range access method but the optimizer estimates that the amount of memory needed for this method would exceed the limit, it abandons the plan and considers other plans. (Bug #70247, Bug #17413040, Bug #17769777)

Empty XML elements having the form <element/> were not handled correctly by the LOAD XML statement. (Bug #67542, Bug #16171518)

As the number of open MyISAM tables increased, lookups to check whether a table was open became expensive, particularly when the table was not open. Lookup performance has been improved, with the overhead reduction especially beneficial for selects on large number of tables with large values of table_open_cache and table_definition_cache. (Bug #49177, Bug #11757169)

Account Management Notes

Backup Notes

Configuration Notes

JSON Notes

Optimizer Notes

Packaging Notes

Performance Schema Notes

Plugin Service Notes

Plugin Notes

Security Notes

Spatial Data Support

SQL Mode Notes

Functionality Added or Changed

Bugs Fixed

The CREATE USER statement now supports an IF NOT EXISTS clause that causes the statement to produce a warning for each named account that already exists, rather than an error. The ALTER USER and DROP USER statements now support an IF EXISTS clause that cause the statements to produce a warning for each named account that does not exist, rather than an error. For details, see CREATE USER Syntax, ALTER USER Syntax, and DROP USER Syntax.

These statement variants can be useful in replication scenarios when the set of accounts differs between master and slave. They also permit scripting account-management operations that otherwise would terminate for statement errors.

The maximum length of MySQL user names has been increased from 16 to 32 characters, which provides greater flexibility in choosing the user name part of MySQL account names. The change affects permitted user names in these contexts:

There are no changes in the client/server protocol, which exchanges user names as null-terminated strings. However, third-party programs that use this protocol to communicate may need to be modified if they use or store user names based on the assumption of 16 characters maximum.

The increase in maximum user name length has implications for MySQL administration:

If you upgrade to this MySQL release from an earlier version, you must run mysql_upgrade (and restart the server) to incorporate this change in user name length.

A new client program, mysqlpump, provides an alternative to mysqldump. Its features include:

For more information, see mysqlpump — A Database Backup Program.

There are some notable differences between mysqlpump and mysqldump:

The default configuration for systemd now sets LimitNOFILE to 5000 to increase the number of file descriptors available to the MySQL server. This change applies to Linux systems on which MySQL installation is performed using RPM packages. On such systems, the number of descriptors available is often set by the operating system to 1024. The change causes the number of descriptors to match the --open-files-limit option default value of 5000. To configure a different number of descriptors, set LimitNOFILE as described at Managing MySQL Server with systemd. (Bug #21073014)

The libmysqld embedded server took its default secure_file_priv value from the INSTALL_SECURE_FILE_PRIVDIR CMake option, but cannot share the same directory with a non-embedded server. The new INSTALL_SECURE_FILE_PRIV_EMBEDDEDDIR option enables a separate directory to be specified for libmysqld. The default value is NULL. (Bug #20770671)

MySQL now supports a native JSON data type that enables efficient access to data in JSON (JavaScript Object Notation) documents. The JSON data type provides these advantages over storing JSON-format strings in a string column:

Along with the JSON data type, a set of SQL functions is available to enable operations on JSON values, such as creation, manipulation, and searching. In addition, the CONVERT() and CAST() functions can convert values between JSON and other types.

For more information, see The JSON Data Type, and JSON Functions.

The optimizer now is able to use indexes on generated columns, even when queries do not refer to such columns directly by name. The optimizer recognizes query expressions that match definitions of generated columns and uses indexes from those columns as appropriate during query execution. For details, see Optimizer Use of Generated Column Indexes.

The optimizer cost model has a new memory_block_read_cost parameter in the mysql.engine_cost table representing the cost of reading an index or data block from an in-memory database buffer.

Together with the existing io_block_read_cost parameter representing the cost of reading a block from disk, this change enables cost models for data access methods to take into account the costs of reading information from different sources; that is, the cost of reading information from disk versus reading information already in a memory buffer. For the initial implementation, the default value of memory_block_read_cost is the same as io_block_read_cost. Tuning the values remains as future work, although you can change the values to see how that affects query performance. For more information, see The Optimizer Cost Model.

If you upgrade to this MySQL release from an earlier version, you must run mysql_upgrade (and restart the server) to incorporate this change into the mysql system database.

The optimizer hint capability introduced in MySQL 5.7.7 has been expanded to subquery execution strategies. Subquery hints affect whether to use semi-join transformations and which semi-join strategies to permit, and, when semi-joins are not used, whether to use subquery materialization or IN-to-EXISTS transformations. Examples:

SELECT /*+ SEMIJOIN(FIRSTMATCH, LOOSESCAN) */ * FROM t1 ...;
SELECT id, a IN (SELECT /*+ SUBQUERY(MATERIALIZATION) */ a FROM t1) FROM t2;
SELECT * FROM t2 WHERE t2.a IN (SELECT /*+ SUBQUERY(INTOEXISTS) */ a FROM t1);

For more information, see Subquery Optimizer Hints.

There is also a new duplicateweedout flag for the optimizer_switch system variable. This flag enables use of optimizer_switch to specify whether to use the Duplicate Weedout semi-join strategy, which was not previously possible.

For Windows, the MSI installer package no longer includes debugging binaries/information components (including PDB files). These are available in a separate Zip archive named mysql-VERSION-winx64-debug-test.zip for 64-bit and mysql-VERSION-win32-debug-test.zip for 32-bit. (Bug #18296012)

Current-event timing now provides more information. Previously, while a wait, stage, statement, or transaction event was executing, the respective tables displayed the event with TIMER_START populated, but with TIMER_END and TIMER_WAIT as NULL:

events_waits_current
events_stages_current
events_statements_current
events_transactions_current

To make it possible to determine how how long a not-yet-completed event has been running, the timer columns now are set as follows:

To find events that have not yet completed (that is, have no END_EVENT_ID) and have taken longer than N picoseconds thus far, monitoring applications can use this expression in queries:

WHERE END_EVENT_ID IS NULL AND TIMER_WAIT > N

(Bug #75156, Bug #20889406)

The Performance Schema incorporates these changes:

If you upgrade to this MySQL release from an earlier version, you must run mysql_upgrade (and restart the server) to incorporate these changes into the performance_schema database.

References: See also: Bug #76167, Bug #20652173, Bug #20684424, Bug #20811494.

MySQL server plugins have access to server “services,” as described in MySQL Services for Plugins. MySQL distributions now include plugins that demonstrate how to test plugin service APIs. The test_framework plugin is a bare bones plugin that shows the minimum required framework for service testing. The test_services and test_services_threaded plugins demonstrate how to test the my_snprintf and my_plugin_log_service services in unthreaded and threaded contexts. For more information, see Plugins for Testing Plugin Services, in The MySQL Test Framework, Version 2.0.

MySQL distributions now provide a locking interface that implements locks with three attributes: Lock namespace, lock name, and lock mode. The namespace enables different applications to use the same lock names without colliding by creating locks in separate namespaces. Locks can be created with a mode of either read (shared) or write (exclusive).

This locking interface is available at two levels: 1) As a C language interface, callable as a plugin service from server plugins or user-defined functions; 2) At the SQL level, as a set of user-defined functions that map onto calls to the service routines. For more information, see The Locking Service.

The interface provided by the locking service is distinct from that provided by GET_LOCK() and related SQL functions (see Miscellaneous Functions). For example, GET_LOCK() does not implement namespaces and provides only exclusive locks, not distinct read and write locks.

The initial implementation for query rewrite plugins used its own API. This API has been reimplemented to use the audit plugin API. For more information, see Writing Audit Plugins. One effect of the query rewrite plugin reimplementation is reduced overhead.

MySQL distributions now include Version Tokens, a feature that enables creation of and synchronization around server tokens that applications can use to prevent accessing incorrect or out-of-date data. Version Tokens is based on a plugin library that implements a version_tokens plugin and a set of user-defined functions. For more information, see Version Tokens.

These changes were made for the Rewriter query rewrite plugin (see The Rewriter Query Rewrite Plugin):

To upgrade if you have previously installed the Rewriter plugin, uninstall it by running the uninstallation script first, then run the installation script. After reinstalling, load your rewrite rules again (this is necessary because uninstalling drops the rules table). For instructions, see Installing or uninstalling the Rewriter Query Rewrite Plugin.

Community Edition RPM packages now invoke mysql_ssl_rsa_setup during installation to create default SSL and RSA key and certificate files. (Bug #20855737)

my_print_defaults now masks passwords. To display passwords in cleartext, use the new --show option. In addition, The output for client programs invoked with the --print-defaults option now masks passwords. (Bug #19953365, Bug #20903330)

A new system variable, require_secure_transport, enables administrators to require all client connections to the server to be made using some form of secure transport. Qualifying connections are TCP/IP connections that use SSL, or connections that use a socket file (on Unix) or shared memory (on Windows). When this variable is enabled, the server rejects nonsecure connection attempts, which fail with an ER_SECURE_TRANSPORT_REQUIRED error.

This capability supplements per-account SSL requirements, which take precedence. For exmaple, if an account is defined with REQUIRE SSL, enabling require_secure_transport does not make it possible to use the account to connect using a Unix socket file.

ST_NumInteriorRing() was added as more a standard-compliant alias of ST_NumInteriorRings(). (Bug #77598, Bug #21362781)

All spatial computations now are done using Boost.Geometry functions. All older non-Boost-based algorithms have been removed. (Bug #77444, Bug #21300713)

Geometry constructor functions that take WKT or WKB values (such as ST_GeomFromText() and ST_GeomFromWKB()) did not check for trailing garbage bytes. They now reject trailing nonwhitespace characters and produce an error. (Bug #77244, Bug #21198064)

The required version of the Boost library for server builds has been raised from 1.57.0 to 1.58.0. (Bug #76354, Bug #20721087)

Geometry object constructor functions such as Point() and MultiPolygon() now are stricter about rejecting invalid arguments. (Bug #76337, Bug #20712775)

In MySQL 5.7.4, the ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE, and NO_ZERO_IN_DATE SQL modes were changed so that they did nothing when named explicitly. Instead, their effects were included in the effects of strict SQL mode (STRICT_ALL_TABLES or STRICT_TRANS_TABLES). The intent was to reduce the number of SQL modes with an effect dependent on strict mode and make them part of strict mode itself.

However, the change to make strict mode more strict by including ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE, and NO_ZERO_IN_DATE caused some problems. For example, in MySQL 5.6 with strict mode but not NO_ZERO_DATE enabled, TIMESTAMP columns can be defined with DEFAULT '0000-00-00 00:00:00'. In MySQL 5.7.4 with the same mode settings, strict mode includes the effect of NO_ZERO_DATE and TIMESTAMP columns cannot be defined with DEFAULT '0000-00-00 00:00:00'. This causes replication of CREATE TABLE statements from 5.6 to 5.7.4 to fail if they contain such TIMESTAMP columns.

The long term plan is still to have the three affected modes be included in strict SQL mode and to remove them as explicit modes in a future MySQL release. But to restore compatibility in MySQL 5.7 with MySQL 5.6 strict mode and to provide additional time for affected applications to be modified, the following changes have been made:

With the preceding changes, stricter data checking is still enabled by default, but the individual modes can be disabled in environments where it is currently desirable or necessary to do so.

Although ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE, and NO_ZERO_IN_DATE again can be used separately from strict mode, it is intended that they be used together. As a reminder, a warning now occurs if they are enabled without also enabling strict mode or vice versa.

References: See also: Bug #75439, Bug #20367829.

InnoDB: The adaptive hash index search system is now partitioned, with each index bound to a specific partition, and each partition protected by a separate latch. Partitioning is controlled by the innodb_adaptive_hash_index_parts configuration option.

Prior to MySQL 5.7.8, the adaptive hash index search system was protected by a single latch (btr_search_latch) which could become a point of contention. To reduce contention, innodb_adaptive_hash_index_parts is set to 8 by default. The maximum setting is 512. (Bug #20985298)

InnoDB: The new innodb_log_checksum_algorithm option specifies how to generate and verify the checksum stored in redo log disk blocks. innodb_log_checksum_algorithm supports same algorithms as innodb_checksum_algorithm, which include innodb, crc32, none, and their associated strict forms. Previously, only the innodb algorithm was supported for redo log disk blocks. innodb_log_checksum_algorithm=innodb is the default setting. Thanks to Alexey Kopytov for the patch. (Bug #20531208, Bug #75595)

InnoDB: InnoDB now supports secondary indexes on virtual generated columns. For more information, see Secondary Indexes and Generated Columns.

InnoDB: Internal server-layer functions were added to allow InnoDB purge threads to construct and destroy thread handle objects, and to compute virtual generated column index values when a table object is not present. This enhancement was required to support secondary indexes on virtual generated columns.

InnoDB: Virtual generated column values no longer occupy space in database rows. With this change, a table rebuild is no longer required when adding or dropping virtual generated columns. Only a system table update is necessary, to register the new metadata.

Virtual generated columns are still represented in InnoDB metadata. The N_COLS field of INNODB_SYS_TABLES still counts virtual generated columns, and INNODB_SYS_COLUMNS still includes virtual generated column metadata.

A new INFORMATION_SCHEMA table, INNODB_SYS_VIRTUAL, provides metadata about columns upon which virtual generated columns are based.

InnoDB: InnoDB now supports page-level compression for file-per-table tablespaces. Page compression is enabled by specifying the COMPRESSION attribute when creating or altering a table. Supported compression algorithms include Zlib and LZ4. This feature, which is referred to as transparent page compression, relies on sparse file and hole punching support. It is supported on Windows with NTFS, and a subset of MySQL-supported Linux platforms where the kernel level provides hole punching support.

For more information about this feature, see InnoDB Page Compression.

InnoDB: The new innodb_flush_sync configuration option, which is enabled by default, causes the innodb_io_capacity setting to be ignored for bursts of I/O activity that occur at checkpoints. To adhere to the limit on InnoDB background I/O activity defined by the innodb_io_capacity setting, disable innodb_flush_sync.

InnoDB: The default value for innodb_purge_threads and innodb_page_cleaners was changed from 1 to 4. If the number of page cleaner threads exceeds the number of buffer pool instances, innodb_page_cleaners is automatically set to the same value as innodb_buffer_pool_instances.

Replication: The behavior of SET GTID_PURGED has been changed so that it does not add any GTIDs to Previous_gtids_log_event and does not rotate the binary log. Instead the GTIDs are added to the mysql.gtid_executed table. This fix ensures that it is safe in all cases to use binlog_gtid_simple_recovery=1 for a server using MySQL 5.7.8 or later, where all binary logs were generated by servers using MySQL 5.7.8 or later. (Bug #75767, Bug #20470724)

Replication: When using a multi-threaded slave, each worker thread has its own queue of transactions to process. In previous MySQL versions, STOP SLAVE waited for all workers to process their entire queue. This logic has been changed so that STOP SLAVE first finds the newest transaction that was committed by any worker thread. Then, it waits for all workers to complete transactions older than that. Newer transactions are not processed. The new logic allows STOP SLAVE to complete faster in case some worker queues contain multiple transactions. (Bug #75525, Bug #20369401)

Solaris tarball and PKG distributions no longer have -gcc in the distribution file names. (Bug #21047137)

Previously, the max_digest_length system variable controlled the maximum digest length for all server functions that computed statement digests. However, whereas the Performance Schema may need to maintain many digest values, other server functions such as query rewrite plugins need only one digest per session. Increasing the max_digest_length value has little impact on total memory requirements for those functions, but can increase Performance Schema memory requirements significantly. To enable configuring digest length separately for the Performance Schema, its digest length is now controlled by the new performance_schema_max_digest_length system variable. (Bug #20963147)

The server now prints more descriptive diagnostic messages for bad values of secure_file_priv. (Bug #20771331)

For attempts to create a multiple-column SPATIAL index, the server previously returned an “Incorrect arguments to SPATIAL INDEX” error. Now it returns ER_TOO_MANY_KEY_PARTS (“Too many key parts specified; max 1 parts allowed”). (Bug #18320371)

For tables that contain object information, the Performance Schema now uses lowercase stored program names. (Bug #17818062)

To make the effect of password-change operations more clear, mysql_secure_installation now displays the user whose password is being changed. (Bug #17343687)

The patch number of the C client library is now increased for each patch version of the server. This number has the format major.minor.patch. (Bug #77544, Bug #21341481)

The max_statement_time system variable was renamed to max_execution_time. The Max_statement_time_exceeded, Max_statement_time_set, and Max_statement_time_set_failed status variables were renamed to Max_execution_time_exceeded, Max_execution_time_set, and Max_execution_time_set_failed.

The MAX_STATEMENT_TIME option for SELECT statements was removed because its functionality is now available using the more general optimizer hint syntax (see Optimizer Hints). Statements that begin like this:

SELECT MAX_STATEMENT_TIME = N ...

Should be rewritten to begin like this:

SELECT /*+ MAX_EXECUTION_TIME(N) */ ...

There are some minor implementation differences between the two. MAX_STATEMENT_TIME was not permitted in non-top-level SELECT statements such as subqueries, or in stored programs, and produced an error. MAX_EXECUTION_TIME() is permitted in those contexts, but is ignored. (Bug #77461, Bug #21306646, Bug #77460, Bug #21306392, Bug #77459, Bug #21306319)

GeometryCollection() with no arguments is now permitted as a way to create an empty geometry. (Bug #77114, Bug #21127270)

The shutdown timeout value in /etc/init.d/mysqld was too short for some environments. The value has been increased from 60 seconds to 600 seconds. (Bug #76900, Bug #20987568)

Use of the optimizer cost model was extended to estimating index scan costs within test_if_cheaper_ordering() for the I/O cost of accessing table blocks. (Bug #76804, Bug #20947871)

For MySQL install operations on OS X from DMG packages, if a a random root account password is generated, it now is displayed in a dialog box. (Bug #76792, Bug #20930305)

mysqldump no longer dumps the sys schema by default. It is still possible to dump it by naming it explicitly on the command line (for example, mysqldump --databases sys). (Bug #76735, Bug #20902791)

For non-TCP/IP connections, these changes were made when --ssl was specified to force SSL to be used:

(Bug #76508, Bug #20785409, Bug #21025587)

mysql_ssl_rsa_setup now has a --uid=name option that enables specifying the owner for any files created by the program (if the program is executed as root). (Bug #76369, Bug #20726413)

MySQL distributions now include an innodb_stress suite of test cases. Thanks to Mark Callaghan for the contribution. (Bug #76347, Bug #20717127)

The data type for generated columns now permits the COLLATE attribute. (Bug #76329, Bug #20709487)

Connections for the FEDERATED storage engine now set the program_name session connection attribute to federated to permit identification of the connection source. (Bug #68781, Bug #16555730)

Previously, changes to the validate_password plugin dictionary file (named by the validate_password_dictionary_file system variable) while the server was running required a restart for the server to recognize the changes. Now validate_password_dictionary_file can be set at runtime and assigning a value causes the named file to be read without a restart.

In addition, two new status variables are available. validate_password_dictionary_file_last_parsed indicates when the dictionary file was last read, and validate_password_dictionary_file_words_count indicates how many words it contains. (Bug #66697, Bug #14588145)

The error produced for a COM_FIELD_LIST command with too much data was changed from ER_UNKNOWN_COM_ERROR to the more informative ER_MALFORMED_PACKET. (Bug #53699, Bug #11761229)

A new system variable, disabled_storage_engines, enables administrators to designate storage engines that cannot be used to create new tables or tablespaces. By default, this variable is empty (no engines disabled), but it can be set to a comma-separated list of one or more engines. Any engine named in the value cannot be used to create tables or tablespaces with CREATE TABLE or CREATE TABLESPACE, and cannot be used with ALTER TABLE ... ENGINE or ALTER TABLESPACE ... ENGINE to change the storage engine of existing tables or tablespaces. Attempts to do so result in an ER_DISABLED_STORAGE_ENGINE error.

disabled_storage_engines does not restrict other DDL statements for existing tables, such as CREATE INDEX, TRUNCATE TABLE, ANALYZE TABLE, DROP TABLE, or DROP TABLESPACE. This permits a smooth transition so that existing tables or tablespaces that use a disabled engine can be migrated to a permitted engine by means such as ALTER TABLE ... ENGINE permitted_engine.

MySQL distributions no longer include the sql-bench directory. The INSTALL_SQLBENCHDIR CMake option has also been removed.

References: See also: Bug #21303289.

The default value of the table_open_cache_instances system variable has been increased from 1 to 16.

The read_only system variable enables the server to be put into read-only mode, in which the server permits client updates only from users who have the SUPER privilege. A new super_read_only system variable, if enabled, prohibits client updates even from users who have SUPER. “Super” read-only mode can be useful for operations such as preparing a server for a move or upgrade because it prevents all client users from modifying data, even administrators.

The so-called “fast mutex” code has been removed from the server sources. It provides no measurable benefit, complicates the code, and is problematic for certain architectures such as POWER8. The (undocumented) WITH_FAST_MUTEXES CMake option has also been removed.

References: See also: Bug #37703, Bug #11748914, Bug #72806, Bug #18871517, Bug #72807, Bug #18871138, Bug #72805, Bug #18870931.

Work was done to clean up the source code base, including: Removal of unneeded CMake checks; removing unused macros from source files; reorganizing header files to reduce the number of dependencies and make them more modular, removal of function declarations without definitions.

mysqld_safe no longer uses the data directory as a possible location for setting MYSQL_HOME. (This has been deprecated since MySQL 5.0.)

Incompatible Change: The mysql_parser plugin service interface defined in the service_parser.h header file was incorrect for the case that the MYSQL_DYNAMIC_PLUGIN macro was defined. The test for this symbol used the wrong name, so the interface did not enable the proper code. The test has been corrected, and some adjustments made to the API for function pointer members within the mysql_parser_service_st structure:

These modifications change the service API. Any plugin to be used with this version of MySQL that relies on the service must be recompiled. (Bug #20856729)

Incompatible Change: Internal storage format for VIRTUAL generated columns was modified. For MyISAM tables with such columns, this is an incompatible change; for upgrades, use ALTER TABLE to drop the columns before the upgrade and add them again after the upgrade. (Bug #77312, Bug #21237637)

Incompatible Change: For multibyte character sets, LOAD DATA could fail to allocate space correctly and ignore input rows as a result. (Bug #76237, Bug #20683959, Bug #23080148)

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

InnoDB; Partitioning: In certain rare cases the optimizer pruned all partitions for an InnoDB table but failed to remove the table from consideration as a source for obtaining matches, instead calling for the table to be initialized and prepared for fetching records. This occurred when the active index was not set during initialization. To fix this problem, we now set the active index ID during initialization even if there are no partitions to select from. This behavior also matches the way the same case is already handled in MySQL 5.6. (Bug #21211524)

InnoDB; Partitioning: Sorted index reads on partitioned InnoDB tables added rows to the prefetch cache, which could cause rows from the wrong partition since the prefetch cache does not support partitioned tables. Now the the prefetch cache is disabled in such cases. (Bug #20584754)

InnoDB; Partitioning: ALTER TABLE ADD UNIQUE INDEX failed when run concurrently with an INSERT on the same partitioned InnoDB table. (Bug #20510811, Bug #75834)

InnoDB; Partitioning: The CREATE_TIME column of the INFORMATION_SCHEMA.TABLES table now shows the correct table creation time for partitioned InnoDB tables. The CREATE_TIME column of the INFORMATION_SCHEMA.PARTITIONS table now shows the correct partition creation time for a partition of partitioned InnoDB tables.

The UPDATE_TIME column of the INFORMATION_SCHEMA.TABLES table now shows when a partitioned InnoDB table was last updated by an INSERT, DELETE, or UPDATE. The UPDATE_TIME column of the INFORMATION_SCHEMA.PARTITIONS table now shows when a partition of a partitioned InnoDB table was last updated. (Bug #69990, Bug #17299181)

InnoDB: With innodb_strict_mode=OFF, a CREATE TEMPORARY TABLE ... ROW_FORMAT=Compressed TABLESPACE=innodb_file_per_table DATA DIRECTORY ... statement raised an assertion. The DATA DIRECTORY clause is not supported with temporary tables and should be ignored. (Bug #21324507, Bug #77495)

InnoDB: The btr_search_drop_page_hash_index function dereferenced the adaptive hash index block before acquiring a latch, which could result in a race condition. (Bug #21310520)

InnoDB: A regression introduced in MySQL 5.7.2 caused an innochecksum-related memory leak. (Bug #21255718)

InnoDB: The records_in_range function returned a constant value for spatial indexes. (Bug #21245805, Bug #77332)

InnoDB: In some cases, memory was not properly allocated for rw_lock_t instances. (Bug #21242541)

InnoDB: SHOW ENGINE INNODB STATUS no longer reports mutex metrics. Mutex metrics are now reported by SHOW ENGINE INNODB MUTEX. (Bug #21238953, Bug #77314)

References: See also: Bug #21052754, Bug #21266784.

InnoDB: Functionality required to build adaptive hash indexes on field prefixes was reintroduced to improve sequential insert performance. The functionality was removed in MySQL 5.7.2 by the fix for Bug #21198396. (Bug #21198396, Bug #77246)

InnoDB: When defining buf_block_t, a lock and a mutex were often accessed in the same vicinity, which could cause unintended cache line sharing. (Bug #21153684)

InnoDB: The ib_cursor_moveto function did not accept a search tuple with fewer fields than are defined for the index. (Bug #21121197, Bug #77083)

InnoDB: The ib_table_truncate function failed to release a transaction, resulting in a hang on server shutdown. (Bug #21121164, Bug #77084)

InnoDB: The ib_open_table_by_id function passed an incorrect argument to dict_table_open_on_id. (Bug #21121084, Bug #77100)

InnoDB: On Unix-like platforms, os_file_create_simple_no_error_handling_func and os_file_create_func opened files in different modes when innodb_flush_method was set to O_DIRECT. (Bug #21113036, Bug #76627)

InnoDB: A cascade operation resulted in a duplicate entry error in FTS_DOC_ID_INDEX. The same document ID was used by two cascade operations. (Bug #21111301, Bug #77087)

InnoDB: Starting the server with an invalid innodb_data_file_path setting did not produce a sufficiently informative error message. (Bug #21103446, Bug #77056)

InnoDB: A regression introduced in MySQL 5.7.5 caused sorting to be skipped when rebuilding a table after dropping a single-column primary key. (Bug #21103101)

InnoDB: Opening a foreign key-referenced table with foreign_key_checks enabled resulted in an error when the table or database name contained special characters. (Bug #21094069, Bug #77043)

InnoDB: The page_zip_verify_checksum function returned false for a valid compressed page. (Bug #21086723)

InnoDB: DDL operations for tablespaces could fail to implicitly commit the current transaction. (Bug #21081898)

InnoDB: The rollback of a partially completed transaction containing more than one update to a spatial index raised an assertion in row_ins_sec_index_entry_by_modify(). (Bug #21076238)

InnoDB: In the case of a lock conflict, shutdown could hang waiting for asynchronous rollback to finish. (Bug #21075892)

InnoDB: To avoid conflicts with implicitly created file-per-table tablespaces, CREATE TABLESPACE ... ADD DATAFILE no longer supports creation of tablespace data files in subdirectories under the MySQL data directory (datadir). Additionally, the data file path specified in a CREATE TABLESPACE ... ADD DATAFILE statement must be an existing directory. InnoDB no longer creates missing directories for CREATE TABLESPACE ... ADD DATAFILE statements. (Bug #21068487, Bug #77002)

InnoDB: SHOW ENGINE INNODB MUTEX functionality, which was removed in MySQL 5.7.2, was revised and added back. Mutex statistics collection can now be configured dynamically using the following options:

For more information, see SHOW ENGINE Syntax.

Sync debug checking for the InnoDB storage engine, previously defined under UNIV_SYNC_DEBUG, is now defined under UNIV_DEBUG and is available when debugging support is compiled in using the WITH_DEBUG CMake option. When debugging support is compiled in, InnoDB sync debug checking is controlled by the innodb_sync_debug configuration option. (Bug #21052754)

InnoDB: A tablespace opened locally by a truncate routine was not closed in protected mode. (Bug #21046968)

InnoDB: An assertion was raised when truncation logic identified inactive undo tablespaces as candidates for undo log truncation. Some undo tablespaces were left inactive when the number of available undo tablespaces exceeded the number of undo logs. (Bug #21046781)

InnoDB: At startup, InnoDB updated the SYS_DATAFILES internal system table with the space_id and path of each system tablespace file even though a record was already present and SYS_DATAFILES.PATH matched the current value. (Bug #21044191)

InnoDB: In Windows debug builds, an innodb_flush_method setting of normal or unbuffered raised an assertion. (Bug #20981684)

InnoDB: Transactions could be subjected to rollback while performing DDL operations. The transactions were not marked as DDL transactions, and TRX_FORCE_ROLLBACK_DISABLE was not set. (Bug #20979020)

InnoDB: An ALTER TABLE ... IMPORT TABLESPACE operation on a table with prefix index failed with a schema mismatch error. (Bug #20977779, Bug #76877)

InnoDB: Initializing the database with an innodb_page_size setting of 64K and a system tablespace data file size less than 12MB raised an assertion. With an InnoDB page size of 64KB, the first system tablespace data file (ibdata1) was not large enough to contain the doublewrite buffer blocks (block1 and block2). To ensure that the doubwrite buffer blocks fit within the first system tablespace data file, a minimum data file size is now enforced. If innodb_page_size is less than or equal to 16KB, the minimum data file size for the first system tablespace data file (ibdata1) is 3MB. For innodb_page_size=32k, the minimum data file size is 6MB. For innodb_page_size=64k, the minimum data file size is 12MB. (Bug #20972309)

InnoDB: Full-text search operations between tables related by a foreign key constraint were not properly cascaded during iterative DML cascading operations. (Bug #20953265, Bug #76817)

InnoDB: In MySQL 5.7.2, 32 of 128 undo logs (rollback segments) were reserved as non-redo undo logs for temporary table transactions. With one of the remaining undo logs always allocated to the system tablespace, 95 undo logs remained available for allocation to the system tablespace or separate undo tablespaces. This change effectively reduced the innodb_undo_tablespaces maximum limit to 95. In other words, a limit of 95 available undo logs also limited the maximum number of undo tablespaces to 95. In MySQL 5.7.8, the innodb_undo_tablespaces maximum value is officially reduced to 95. (Bug #20938115)

InnoDB: A memory leak occurred when a foreign key constraint object was loaded with the parent table while the child table failed to load. The foreign key constraint object should only be loaded with the child table. (Bug #20926253, Bug #21041449)

InnoDB: Debug only code set m_prebuilt, which may affect in-place ALTER TABLE behaviour. m_prebuilt to should not be used to store an intermediate value in debug-only code. (Bug #20921940, Bug #76774)

InnoDB: The definition of the fil_node_t data structure was moved from fil0fil.cc to fil0fil.h so that diagnostic code outside that module can access information about files that belong to a tablespace. (Bug #20886222, Bug #76694)

InnoDB: Assertion code was revised to avoid compiler warnings that occurred when compiling MySQL on OS X 10.10.2. (Bug #20883256, Bug #76690)

InnoDB: After upgrading to MySQL 5.7.6 or later, restarting the server after truncating a table that was originally created in MySQL 5.7.5 or earlier raised an “incorrect MERGE_THRESHOLD length in SYS_INDEXES” error. A MERGE_THRESHOLD column was added to the internal SYS_INDEXES table in MySQL 5.7.6. SYS_INDEXES records for tables that were not rebuilt or imported after upgrading did not include the new column. The TRUNCATE TABLE operation updated the table's SYS_INDEXES records to include the new column but set the MERGE_THRESHOLD value to NULL. (Bug #20882432)

InnoDB: A failure to load a change buffer bitmap page during a concurrent delete tablespace operation caused a server exit. (Bug #20878735)

InnoDB: A shutdown hang occurred when an innodb_force_recovery setting of 3 or higher prevented the rollback of transactions that were in an ACTIVE state. ACTIVE transactions are now placed in XA PREPARE state in the main-memory data structure to allow shutdown to proceed normally. The transactions are recovered as ACTIVE on the next restart and are rolled back unless innodb_force_recovery is again set to 3 or higher. (Bug #20874411)

InnoDB: If a server exit occurred during an XA ROLLBACK, the transaction was incorrectly recovered in XA PREPARE state. As a result, subsequent XA COMMIT transactions were possible, which would break ACID compliance and potentially cause corruption between indexes of a table. (Bug #20872655, Bug #76672)

InnoDB: A CREATE TABLESPACE operation raised a Valgrind error due to a memory leak in the os_create_subdirs_if_needed function. (Bug #20865674)

InnoDB: Calls to buf_page_print() were removed to avoid filling mysql-test-run logs with InnoDB page dumps. Page dumps related to file I/O are still printed. (Bug #20863042)

InnoDB: CREATE TABLESPACE failed to move internal tablespace files to a reserved name space that starts with an innodb_ prefix, permitting internal tablespace files to be dropped. (Bug #20840368, Bug #76603)

InnoDB: A TRUNCATE TABLE operation on a general tablespace table with a full-text search index raised an assertion. (Bug #20834483)

InnoDB: An assertion was raised on shutdown due to XA PREPARE transactions holding explicit locks. (Bug #20816223, Bug #76567)

InnoDB: The fts_print_doc_id function printed too much debug information in debug builds. fts_enable_diag_print is now used instead. (Bug #20811125)

InnoDB: After a failed DROP TABLE operation, the purge background thread asserted while attempting to access an index page of the table. Purge should not attempt to clean a table that is marked as corrupt. Purge now checks for a corrupt primary index. (Bug #20789078, Bug #75913)

InnoDB: A checksum mismatch error on a crc32 checksum was encountered when restarting the server on a data file copied from a machine with a different endianness. The crc32 checksum should be recognized regardless of the native byte order of the system where the checksum was generated. (Bug #20783098, Bug #76375)

InnoDB: An ALTER TABLE ... DROP INDEX operation on a table with foreign key dependencies raised an assertion. (Bug #20768847)

InnoDB: An assertion was raised when InnoDB attempted to dereference a NULL foreign key object. (Bug #20762798)

InnoDB: An ALTER TABLE operation raised an assertion due a regression introduced in MySQL 5.7.6 with the introduction of native partitioning support for general tablespaces. (Bug #20759613)

InnoDB: In some instances, functions that call DBUG_ENTER did not call DBUG_RETURN. (Bug #20753620, Bug #76447)

InnoDB: A regression of the trx_is_started function in MySQL 5.7.6 caused a shutdown hang. (Bug #20744155)

InnoDB: The MeCab full-text plugin parser failed to handle an out-of-memory exception. (Bug #20742590)

InnoDB: An assertion was raised during a rollback operation due to a record the was incorrectly undelete-marked. (Bug #20734998)

InnoDB: An assertion was raised in a debug build when an ALTER TABLE operation invoked obsolete foreign key code while attempting to create an optimized temporary table as part of an optimizer plan. Temporary tables do not support foreign keys. Invocation of foreign key code is now blocked for optimized temporary tables. (Bug #20730289)

InnoDB: An INSERT operation raised an assertion. The calculation that determines the number of extents to reserve when storing a BLOB did account for compressed pages. (Bug #20713559)

InnoDB: Missing brackets in the fsp_flags_is_valid function could result in a failure to recognize a corrupted data file. (Bug #20671465)

InnoDB: A query that used a percentage character '%' as the last character in a query token raised a full-text parser plugin assertion. Full-text parser plugins created using the full-text parser plugin framework now ignore the '%' character if specified as the first or last character in a query token. Using the '%' character as the first character in a query token is not permitted by the internal SQL parser. Using the '%' character as last character in a query token is reserved for prefix matching. (Bug #20668156)

InnoDB: The INFORMATION_SCHEMA.FILES table now reports metadata for all InnoDB tablespace types including file-per-table tablespaces, general tablespaces, the system tablespace, temporary table tablespaces, and undo tablespaces (if present). System tablespace and temporary table tablespace metadata is no longer reported by the INFORMATION_SCHEMA.INNODB_SYS_TABLESPACES and INFORMATION_SCHEMA.INNODB_SYS_DATAFILES tables. However, these tables continue to provide metadata for file-per-table and general tablespaces. (Bug #20660744, Bug #21086257, Bug #77032, Bug #76182)

InnoDB: The InnoDB full-text search feature with the mecab parser plugin would print an empty error message. (Bug #20651493, Bug #76164)

InnoDB: Importing a tablespace with a full-text index resulted in an assertion when attempting to rebuild the index. (Bug #20637494)

InnoDB: A DML operation raised an assertion in btr_estimate_n_rows_in_range(). The assertion code was too strict. (Bug #20618309)

InnoDB: Defining a user-created FTS_DOC_ID column as a primary key produced incorrect full-text search relevancy rankings. (Bug #20597981)

InnoDB: During a table import operation, an INSERT failed with a duplicate key error on an AUTO_INCREMENT column due to an incorrectly initialized AUTO_INCREMENT value. (Bug #20597821, Bug #76037)

InnoDB: After dropping a full-text search index, the hidden FTS_DOC_ID and FTS_DOC_ID_INDEX columns prevented online DDL operations. (Bug #20590013, Bug #76012)

InnoDB: An assertion was raised on server startup when InnoDB tried to create a temporary file in a non-existent temporary directory (tmpdir) while in read-only mode. (Bug #20578834)

InnoDB: The innodb_checksum_algorithm strict_* settings (strict_none, strict_innodb, and strict_crc32) caused the server to halt when InnoDB encountered a valid but non-matching checksum. For example, with innodb_checksum_algorithm=strict_crc32, a valid innodb checksum would cause the server to halt. Now, instead of halting the server, InnoDB only prints an error message. (Bug #20568464)

InnoDB: After moving the MySQL data directory and modifying the datadir configuration parameter to point to the new location, tables stored in general tablespaces failed to open because the tablespace data file could not be found. To address this problem, CREATE TABLESPACE ... ADD DATAFILE now creates an isl file in the MySQL data directory when a general tablespace data file is created outside of the MySQL data directory. Also, the fil_ibd_open function now searches for general tablespaces in the same way that it searches for file-per-table tablespaces. (Bug #20563954)

InnoDB: General tablespaces created on Windows using a relative data file path could not be opened on Unix-like systems. InnoDB failed to convert the backslash (“\”) directory separator that is used in the Windows version of the relative data file path. (Bug #20555168)

InnoDB: General tablespaces now support partitioned InnoDB tables, and individual partitions and subpartitions can now be assigned to a general tablespace. SHOW CREATE TABLE output was revised to include quotes around the tablespace identifier. (Bug #20554858, Bug #20588947)

InnoDB: An ALTER TABLE operation that added a spatial index caused the server to exit. (Bug #20547644)

InnoDB: Assertion code which checks for the lowest possible page number for a tablespace did not account for general tablespaces. (Bug #20544581, Bug #20810627)

InnoDB: The InnoDB memcached plugin handled unsigned NOT NULL integer columns incorrectly. Thanks to Piotr Jurkiewicz for the patch. (Bug #20535517, Bug #75864)

InnoDB: The following changes were implemented for full-text index auxiliary tables:

(Bug #20527217, Bug #75869)

InnoDB: The memcached set command permitted a negative expire time value. Expire time is stored internally as an unsigned integer. A negative value would be converted to a large number and accepted. The maximum expire time value is now restricted to INT_MAX32 to prevent negative expire time values. (Bug #20478242, Bug #75790)

InnoDB: An interrupted ALTER TABLE operation that rendered a child table unavailable caused an error and debug assertion after crash recovery, when the ALTER TABLE operation on the parent table detected that the foreign keys of the parent table could not be loaded. The debug assertion was removed and the error was replaced by a warning. (Bug #20476395)

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

InnoDB: In debug builds, enabling the btr_cur_limit_optimistic_insert_debug flag raised a deadlock exception in the change buffer clustered index. (Bug #20459905, Bug #75736)

InnoDB: A warning message is now printed if DB_TRX_ID stored in a record is found to be greater than max_trx_id. In debug builds, an assertion is raised. (Bug #20445525)

InnoDB: Estimates for the number of records in a range for a given dataset could differ depending on the page size. (Bug #20427694)

InnoDB: During shutdown on Windows, the listener object in handle_shutdown() was freed while the listener was running, resulting in an exception in buf_pool_from_bpage(). (Bug #20421223)

InnoDB: SHOW ENGINE INNODB STATUS output showed negative reservation and signal count values due to a counter overflow error. (Bug #20417397)

InnoDB: Failure to check the status of a cursor transaction read-only option before reusing the cursor transaction for a write operation resulted in a server exit during a memcached workload. (Bug #20391552)

InnoDB: An assertion was raised in a debug build when populating a spatial index during an ALTER TABLE operation. The size of data tuples for compressed rows is calculated in the rec_get_converted_size_comp_prefix_low function. Debug code within the function did not account for the spatial index or the DATA_SYS_CHILD data type in the node pointers. (Bug #20372749)

InnoDB: CHECK TABLE returned a “wrong count” error for tables with spatial indexes. (Bug #20313067)

InnoDB: MDL locks taken by memcached clients caused a MySQL Enterprise Backup FLUSH TABLES WITH READ LOCK operation to hang. (Bug #20275612)