| 更新日誌 |
# Bugs Fixed
- InnoDB: MySQL failed to build on Fedora 24 using GCC 6.
- InnoDB: Potential buffer overflow issues were corrected for the InnoDB memcached plugin.
- InnoDB: The full-text index cache was freed during a background index cache synchronization.
- InnoDB: A full-text index operation raised an assertion.
- 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: With innodb_autoinc_lock_mode=0, multiple threads waiting for a table-level lock caused an unexpected deadlock.
- InnoDB: A FLUSH TABLES ... FOR EXPORT operation appeared to stall. A loop in the ibuf_contract_in_background function failed to exit.
- 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.
- 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.
- 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.
- 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.
- For debug builds, CONCAT_WS() could raise an assertion if there was nothing to append.
- Invoking Enterprise Encryption functions in multiple threads simultaneously could cause a server exit.
- Attempting to use Enterprise Encryption functions after creating and dropping them could cause a server exit.
- Setting sort_buffer_size to a very large value could cause some operations to fail with an out-of-memory error.
- An assertion could be raised when a deadlock occurred due to a SELECT ... GROUP BY ... FOR UPDATE query executed using a Loose Index Scan.
- Several potential buffer overflow issues were corrected.
- 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.
- 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.
- On Windows, MySQL installation could result in MySQL being placed under C:Program FilesCanonEasy-WebPrint EX.
- 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.
- MySQL did not compile under Solaris 12 using Sun Studio. To correct this, instances of __attribute__ were changed to MY_ATTRIBUTE.
- The INSTALL-SOURCE file had partly outdated information and has been removed from source packages. (Binary packages are unaffected).
- For a server compiled with -DWITH_PERFSCHEMA_STORAGE_ENGINE=0, a memory leak could occur for buffered log messages used during server startup.
- For debug builds, merging a derived table into an outer query block could raise an assertion.
- A null pointer dereference of a parser structure could occur during stored procedure name validation.
- Using CREATE USER to create an account with the mysql_native_password or mysql_old_password authentication plugin and using a clause of the form IDENTIFIED WITH plugin AS 'hash_string' caused the account to be created without a password.
- Failure of UNINSTALL PLUGIN could lead to inaccurate or confusing errors for subsequent INSTALL PLUGIN operations.
- mysqld_multi displayed misleading error messages when it was unable to execute my_print_defaults.
- On Windows, MySQL installation failed if the HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionUninstall registry key was present with a key/value pair of "InstallLocation" and "Hewlett-Packard\".
- mysqldump failed silently with no error message when it encountered an error while executing FLUSH LOGS.
|
