オリジナル版：http://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-1.html
MySQL 5.7.1(マイルストーンリリース)は世界でもっともポピュラーなオープンソースデータベースの新しいバージョンです。これはMySQL 5.7の最初のマイルストーンリリースです。
href="http://dev.mysql.com/doc/mysql-development-cycle/en/development-milestone-releases.html" target="_blank">http://dev.mysql.com/doc/mysql-development-cycle/en/development-milestone-releases.html
このリリースの新機能はベータ品質です。他のプロダクションリリース前と同様にプロダクションレベルのシステムやクリティカルなデータを持つシステムにインストールする場合には十分に注意すべきです。
MySQL 5.7.1はMySQL 5.6のすべての機能を含んでいます
新しいサーバへMySQL 5.7.1をインストールする情報として、以下のMySQLのインストールドキュメントを参照してください。
http://dev.mysql.com/doc/refman/5.7/en/installing.html
MySQL Server 5.7.1は、ダウンロード・ページの開発リリースセクションから、ソースコードと多くのプラットフォームのためのバイナリをご利用いただけます。
http://dev.mysql.com/downloads/
MySQL 5.7.1で利用できるプラットフォームとパッケージのフォーマットはMySQL 5.6と同じです。
WindowsパッケージはWindowsインストーラーのための新しいインストーラ、もしくはZIP(ノンインストール)パッケージが利用いただけます。以前のMSIパッケージはもう利用できず、ポイントアンドクリック設定ウィザードと全てのMySQL製品でWindows向けの統一インストーラが利用可能なことに注意してください：
http://dev.mysql.com/downloads/installer/
新規リリースされたMySQl 5.6.11と同様、5.7.1は完全なインストーラーの代替としてWebインストーラーも同梱されています
Webインストーラーは実際の製品すべてにバンドルされているわけではなく、インストールのために洗濯したダウンロードオンデマンドの製品を選択したときにのみ同梱されます。これは最初にダウンロードするサイズを小さくしますが、個々のプロダクトをダウンロードする必要があるため、インストール時間は長くなります。
私たちはフィードバック、バグレポート、バグ修正パッチ等を歓迎します
http://bugs.mysql.com/report.php
次の節では、開発開始から、そして5.6.10には含まれていないバグの修正、MySQL 5.7の変更を記載しています。これはオンラインでも閲覧できます。
http://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-1.html
Changes in MySQL 5.7.1 (23 April 2013, Milestone 11)
Note
This is a milestone release, for use at your own risk. Significant
development changes take place in milestone releases and you may
encounter compatibility issues, such as data format changes that
require attention in addition to the usual procedure of running
mysql_upgrade. For example, you may find it necessary to dump your
data with mysqldump before the upgrade and reload it afterward.
Functionality Added or Changed
* Performance: String hashing overhead was reduced. This also
improves performance for metadata locking, the table
definition cache, and Performance Schema table I/O and file
I/O instrumentation. (Bug #13944392)
* Incompatible Change: SHOW ENGINE PERFORMANCE_SCHEMA STATUS
output used a mix of row_count and count attributes. These are
now all count. Similarly, the output used a mix of row_size
and size attributes. These are now all size. (Bug #16165468)
* InnoDB: Online index renaming is supported by ALTER TABLE,
which now includes a RENAME INDEX clause, as shown in the
following example: "ALTER TABLE t RENAME INDEX i1 TO i2",
where i1 is the current name of the index and i2 is the new
name.
The result of "ALTER TABLE t RENAME INDEX i1 TO i2" would be a
table with contents and structure that is identical to the old
version of "t1" except for the index name, which is now "i2"
instead of "i1".
* InnoDB: You can now increase VARCHAR size online through ALTER
TABLE ...ALGORITHM=INPLACE, CHANGE COLUMN...VARCHAR(). VARCHAR
size may be increased from a value less than 255 bytes up to a
value equal to or less than 255 bytes. You may also increase
VARCHAR size online from a starting value greater than 255
bytes (Bug#15863023).
Note
Decreasing VARCHAR size online is not supported, nor is
increasing VARCHAR size online from a value less than 256
bytes to a value greater than 256 bytes.
* InnoDB: DDL performance for InnoDB temporary tables is
improved through optimization of CREATE TABLE, DROP TABLE,
TRUNCATE TABLE, ALTER TABLE ... IMPORT TABLESPACE, and ALTER
TABLE ...DISCARD TABLESPACE statements.
* InnoDB: Added support for spatial data types currently
supported by MySQL including POINT, LINE_STRING, POLYGON,
MULTI_POINT, MULTI_POLYGON, MULTI_LINE_STRING,
GEOMETRY_COLLECTION, and GEOMETRY.
Prior to this release, InnoDB would store spatial data, except
for POINT, as binary BLOB data. BLOB remains the underlying
data type but spatial data types are now mapped to a new
InnoDB internal data type, DATA_GEOMETRY. With BLOB as the
underlying data type, a prefix index can still be used on the
GEOMETRY data column.
* InnoDB: Added a separate tablespace for all non-compressed
user and system-generated temporary tables. The new
tablespace, which is always recreated on server startup,
provides persistent storage for temporary table
meta-information. Persistent meta-information enables proper
cleanup in crash recovery scenarios. Additionally, a separate
tablespace for temporary tables avoids having to store
persistent meta-information in system tablespaces.
The new tablespace, ibtmp1, is located in the /tmp directory
by default. A newly added configuration file option,
--innodb_temp_data_file_path, allows for a user-defined
temporary data file path.
* Replication: An Auto_Position column has been added to the
output generated by SHOW SLAVE STATUS. The value of this
column shows whether replication autopositioning is in use. If
autopositioning is enabled---that is, if MASTER_AUTO_POSITION
= 1 was set by the last successful CHANGE MASTER TO statement
that was executed on the slave---then the column's value is 1;
if not, then the value is 0. (Bug #15992220)
* Replication: The functions GTID_SUBTRACT() and GTID_SUBSET()
were formerly available in libmysqld only when it was built
with replication support. Now these functions are always
available when using this library, regardless of how it was
built.
* MySQL no longer uses the default OpenSSL compression. (Bug
#16235681)
* There is now a distinct error code
(ER_MUST_CHANGE_PASSWORD_LOGIN) for the error sent by the
server to a client authenticating with an expired password.
(Bug #16102943)
* In RPM packages built for Unbreakable Linux Network,
libmysqld.so now has a version number. (Bug #15972480)
* Error messages for ALTER TABLE statement using a LOCK or
ALGORITHM value not supported for the given operation were
very generic. The server now produces more informative
messages. (Bug #15902911)
* If a client with an expired password connected but
old_passwords was not the value required to select the
password hashing format appropriate for the client account,
there was no way for the client to determine the proper value.
Now the server automatically sets the session old_passwords
value appropriately for the account password. (Bug #15892194)
* mysql_config_editor now supports --port and --socket options
for specifying TCP/IP port number and Unix socket file name.
(Bug #15851247)
* mysqldump now supports an --ignore-error option. The option
value is a comma-separated list of error numbers specifying
the errors to ignore during mysqldump execution. If the
--force option is also given to ignore all errors, --force
takes precedence. (Bug #15855723)
* mysqlcheck has a new --skip-database option. The option value
is the name of a database (case sensitive) for which checks
should be skipped.
mysql_upgrade uses this option to upgrade the system tables in
the mysql database before tables in other databases: It
upgrade the mysql database, then all databases except the
mysql database. This avoids problems that can occur if user
tables are upgraded before the system tables. (Bug #14697538)
* The validate_password_policy_number system variable was
renamed to validate_password_policy. (Bug #14588121)
* Previously, on Linux the server failed to perform stack
backtrace attempts for versions of glibc older than the
current minimum supported version (2.3). Now on such attempts
the server displays a message that the glibc version is too
old to support backtracing. (Bug #14475946)
* In JSON-format EXPLAIN output, the attached_condition
information for subqueries now includes select# to indicate
the relative order of subquery execution. (Bug #13897507)
* The following changes were made to the sandbox mode that the
server uses to handle client connections for accounts with
expired passwords:
+ There is a new disconnect_on_expired_passwords system
variable (default: enabled). This controls how the server
treats expired-password accounts.
+ Two flags were added to the C API client library:
MYSQL_OPT_CAN_HANDLE_EXPIRED_PASSWORDS for
mysql_options() and CLIENT_CAN_HANDLE_EXPIRED_PASSWORDS
for mysql_real_connect(). Each flag enables a client
program to indicate whether it can handle sandbox mode
for accounts with expired passwords.
MYSQL_OPT_CAN_HANDLE_EXPIRED_PASSWORDS is enabled for
mysqltest unconditionally, for mysql in interactive mode,
and for mysqladmin if the first command is password.
For more information about how the client-side flags interact
with disconnect_on_expired_passwords, see Password Expiration
and Sandbox Mode
(http://dev.mysql.com/doc/refman/5.7/en/password-expiration.ht
ml). (Bug #67568, Bug #15874023)
* If a user attempted to access a nonexistent column for which
the user had no access, the server returned an error
indicating that the column did not exist. Now the server
returns an error indicating that the user does not have
privileges for the column, which provides no information about
column existence. (Bug #19947, Bug #11745788)
* The deprecated innodb_mirrored_log_groups system variable has
been removed.
* The mysql client now has a --syslog option that causes
interactive statements to be sent to the system syslog
facility. Logging is suppressed for statements that match the
default "ignore" pattern list ("*IDENTIFIED*:*PASSWORD*"), as
well as statements that match any patterns specified using the
--histignore option. For more information, see mysql Logging
(http://dev.mysql.com/doc/refman/5.7/en/mysql-logging.html).
* ALTER TABLE now supports a RENAME INDEX clause that renames an
index. The change is made in place without a table-copy
operation. See ALTER TABLE Syntax
(http://dev.mysql.com/doc/refman/5.7/en/alter-table.html).
* Important Change; Replication: Added the --idempotent option
for mysqlbinlog, which causes the MySQL Server to employ
idempotent mode. This causes suppression of all duplicate-key
and key-not-found errors when processing updates from the
binary log. The mode is in effect for the current mysqlbinlog
client and client session only.
* Important Change; Replication: SHOW SLAVE STATUS when run
concurrently with STOP SLAVE can take a long time to execute
if the slave SQL thread was in the midst of applying a large
update. To fix this problem, a new NONBLOCKING option has been
added to the SHOW SLAVE STATUS statement. When this option is
used, SHOW SLAVE STATUS does not wait on the SQL or I/O
threads but returns immediately. This means that the reported
states of these threads may not be completely up to date when
the option is used. NONBLOCKING is intended primarily for use
by monitoring tools in which obtaining an immediate response
is more important than having the most timely data.
* Microsoft Windows: Windows Vista, Windows Server 2008, and
newer support native symlinking using the mklink command. This
makes the MySQL Server implementation of database symbolic
links using .sym files redundant, so that mechanism is now
removed. This change has the following implications:
+ Existing .sym files are now ignored. Database symlinks
should be recreated using mklink. See Using Symbolic
Links for Databases on Windows
(http://dev.mysql.com/doc/refman/5.7/en/symbolic-links.ht
ml#windows-symbolic-links).
+ The --symbolic-links and --skip-symbolic-links options
and the have_symlink system variable now are meaningful
only for Unix systems, and not for Windows.
* The server now issues a warning if an index is created that
duplicates an existing index, or an error in strict SQL mode.
(Bug #37520, Bug #11748842)
* Previously, Control+C in mysql interrupted the current
statement if there was one, or exited mysql if not. Now
Control+C interrupts the current statement if there was one,
or cancels any partial input line otherwise, but does not
exit. (Bug #66583, Bug #14554568)
* The mysql_clear_password cleartext client-side authentication
plugin is intended for authentication schemes that require the
server to receive the password as entered on the client side,
without hashing. Because the password is sent in the clear,
this plugin should be used within the context of a secure
connection, such as an SSL connection, to avoid exposing the
password over the network. To make inadvertent use of this
plugin less likely, it is now required that clients explicitly
enable it. This can be done several ways:
+ Set the LIBMYSQL_ENABLE_CLEARTEXT_PLUGIN environment
variable to a value that begins with 1, Y, or y. This
enables the plugin for all client connections.
+ The mysql, mysqladmin, and mysqlslap client programs
support an --enable-cleartext-plugin option that enables
the plugin on a per-invocation basis.
+ The mysql_options() C API function supports a
MYSQL_ENABLE_CLEARTEXT_PLUGIN option that enables the
plugin on a per-connection basis. Also, any program that
uses libmysqlclient and reads option files can enable the
plugin by including an enable-cleartext-plugin option in
an option group read by the client library.
* INSERT DELAYED is no longer supported. The server recognizes
but ignores the DELAYED keyword, handles the insert as a
nondelayed insert, and generates an
ER_WARN_LEGACY_SYNTAX_CONVERTED warning. ("INSERT DELAYED is
no longer supported. The statement was converted to INSERT.").
Similarly, REPLACE DELAYED is handled as a nondelayed replace.
The DELAYED keyword will be removed in a future release.
In addition, several DELAYED-related options or features were
removed:
+ The --delayed-insert option for mysqldump.
+ The COUNT_WRITE_DELAYED, SUM_TIMER_WRITE_DELAYED,
MIN_TIMER_WRITE_DELAYED, AVG_TIMER_WRITE_DELAYED, and
MAX_TIMER_WRITE_DELAYED columns of the Performance Schema
table_lock_waits_summary_by_table table.
If you upgrade to this release of MySQL from an earlier
version, you must run mysql_upgrade (and restart the
server) to incorporate these changes into the
performance_schema database.
+ mysqlbinlog no longer writes comments mentioning INSERT
DELAYED.
* MySQL now supports stacked diagnostics areas and GET STACKED
DIAGNOSTICS can be used during condition handler activation to
retrieve information from the diagnostics area that was
current before the handler was activated. This enables
handlers to inspect information about the condition that
caused the handler to activate. As before, GET [CURRENT]
DIAGNOSTICS still retrieves information about the current
diagnostics area and can be used even if no handler is active.
For more information, see GET DIAGNOSTICS Syntax
(http://dev.mysql.com/doc/refman/5.7/en/get-diagnostics.html).
Bugs Fixed
* Performance; InnoDB: The DROP TABLE statement for a table
using compression
(http://dev.mysql.com/doc/refman/5.7/en/glossary.html#glos_com
pression) could be slower than necessary, causing a stall for
several seconds. MySQL was unnecessarily decompressing pages
(http://dev.mysql.com/doc/refman/5.7/en/glossary.html#glos_pag
e) in the buffer pool
(http://dev.mysql.com/doc/refman/5.7/en/glossary.html#glos_buf
fer_pool) related to the table as part of the DROP operation.
(Bug #16067973)
* Incompatible Change; Partitioning: Changes in the KEY
partitioning hashing functions used with numeric, date and
time, ENUM, and SET columns in MySQL 5.5 makes tables using
partitioning or subpartitioning by KEY on any of the affected
column types and created on a MySQL 5.5 or later server
incompatible with a MySQL 5.1 server. This is because the
partition IDs as calculated by a MySQL 5.5 or later server
almost certainly differ from those calculated by a MySQL 5.1
server for the same table definition and data as a result of
the changes in these functions.
The principal changes in the KEY partitioning implementation
in MySQL 5.5 resulting in this issue were as follows: 1. The
hash function used for numeric and date and time columns
changed from binary to character-based. 2. The base used for
hashing of ENUM and SET columns changed from latin1 ci
characters to binary.
The fix involves adding the capability in MySQL 5.5 and later
to choose which type of hashing to use for KEY partitioning,
which is implemented with a new ALGORITHM extension to the
PARTITION BY KEY option for CREATE TABLE and ALTER TABLE.
Specifying PARTITION BY KEY ALGORITHM=1 ([columns]) causes the
server to use the hashing functions as implemented in MySQL
5.1; using ALGORITHM=2 causes the server to use the hashing
functions from MySQL 5.5 and later. ALGORITHM=2 is the
default. Using the appropriate value for ALGORITHM, you can
perform any of the following tasks:
+ Create KEY partitioned tables in MySQL 5.5 and later that
are compatible with MySQL 5.1, using CREATE TABLE ...
PARTITION BY KEY ALGORITHM=1 (...).
+ Downgrade KEY partitioned tables that were created in
MySQL 5.5 or later to become compatible with MySQL 5.1,
using ALTER TABLE ... PARTITION BY KEY ALGORITHM=1 (...).
+ Upgrade KEY partitioned tables originally created in
MySQL 5.1 to use hashing as in MySQL 5.5 and later, using
ALTER TABLE ... PARTITION BY KEY ALGORITHM=2 (...).
Important: After such tables are upgraded, they cannot be
used any longer with MySQL 5.1 unless they are first
downgraded again using ALTER TABLE ... PARTITION BY KEY
ALGORITHM=1 (...) on a MySQL server supporting this
option.
This syntax is not backward compatible, and causes errors in
older versions of the MySQL server. When generating CREATE
TABLE ... PARTITION BY KEY statements, mysqldump brackets any
occurrence of ALGORITHM=1 or ALGORITHM=2 in conditional
comments such that it is ignored by a MySQL server whose
version is not at least 5.5.31. An additional consideration
for upgrades is that MySQL 5.6 servers prior to MySQL 5.6.11
do not ignore the ALGORITHM option in such statements when
generated by a MySQL 5.5 server, due to the that the
conditional comments refer to version 5.5.31; in this case,
you must edit the dump manually and remove or comment out the
option wherever it occurs before attempting to load it into a
MySQL 5.6.10 or earlier MySQL 5.6 server. This is not an issue
for dumps generated by MySQL 5.6.11 or later version of
mysqldump, where the version used in such comments is 5.6.11.
For more information, see ALTER TABLE Partition Operations
(http://dev.mysql.com/doc/refman/5.7/en/alter-table-partition-
operations.html).
As part of this fix, a spurious assertion by InnoDB that a
deleted row had previously been read, causing the server to
assert on delete of a row that the row was in the wrong
partition, was also removed. (Bug #14521864, Bug #66462, Bug
#16093958, Bug #16274455)
References: See also Bug #11759782.
* Important Change; Plugin API; Replication: Because the
behavior of the fulltext plugin may vary between MySQL
servers, it is not possible to guarantee that statements using
this plugin produce the same results on masters and slaves.
For this reason, statements depending on the fulltext plugin
are now marked as unsafe for statement-based logging. This
means that such statements are logged using row format when
binlog_format=MIXED, and cause a warning to be generated when
binlog_format=STATEMENT. (Bug #11756280, Bug #45449)
* Important Change; Replication: Executing a statement that
performs an implicit commit but whose changes are not logged
when gtid_next is set to any value other than AUTOMATIC is not
permitted. Now in such cases, the statement fails with an
error. This includes the statements in the following list:
+ CHANGE MASTER TO
+ START SLAVE
+ STOP SLAVE
+ REPAIR TABLE
+ OPTIMIZE TABLE
+ ANALYZE TABLE
+ CHECK TABLE
+ CREATE SERVER
+ ALTER SERVER
+ DROP SERVER
+ CACHE INDEX
+ LOAD INDEX INTO CACHE
+ FLUSH
+ RESET
(Bug #16062608)
References: See also Bug #16484323.
* Important Change; Replication: The version number reported by
mysqlbinlog --version has been increased to 3.4. (Bug
#15894381, Bug #67643)
* Important Change; Replication: The lettercasing used for
displaying UUIDs in global transaction identifiers was
inconsistent. Now, all GTID values use lowercase, including
those shown in the Retrieved_Gtid_Set and Executed_Gtid_Set
columns from the output of SHOW SLAVE STATUS. (Bug #15869441)
* Important Note; Replication: It was possible to replicate from
a table to a same-named view using statement-based logging,
while using row-based logging instead led to a failure on the
slave. Now the target object type is checked prior to
performing any DML, and an error is given if the target on the
slave is not actually a table. This is true regardless of the
binary logging format in use. (Bug #11752707, Bug #43975)
* InnoDB: When parsing a delimited search string such as
"abc-def" in a full-text search, InnoDB now uses the same word
delimiters as MyISAM. (Bug #16419661)
* InnoDB: This fix improves code readability by addressing
naming inconsistencies for InnoDB PERFORMANCE_SCHEMA key
declarations. (Bug #16414044)
* InnoDB: This fix disables a condition for extra splitting of
clustered index leaf pages, on compressed tables. Extra page
splitting was only done to reserve space for future updates,
so that future page splits could be avoided. (Bug #16401801)
* InnoDB: For InnoDB tables, if a PRIMARY KEY on a VARCHAR
column (or prefix) was empty, index page compression could
fail. (Bug #16400920)
* InnoDB: Status values in the INNODB_FT_CONFIG table would not
update. The INNODB_FT_CONFIG is intended for internal
configuration and should not be used for statistical
information purposes. To avoid confusion, column values that
are intended for internal use have been removed from the
INNODB_FT_CONFIG table. This fix also removes the
INNODB_FT_INSERTED table and other internal full text
search-related tables that were unintentionally exposed. (Bug
#16409494)
* InnoDB: With innodb_api_enable_mdl=OFF, an ALTER TABLE
operation on an InnoDB table that required a table copy could
cause a server exit. (Bug #16287411)
* InnoDB: Improper testing of compatibility between the
referencing and referenced during ALTER TABLE ... ADD FOREIGN
key could cause a server exit. (Bug #16330036)
* InnoDB: Rollback did not include changes made to temporary
tables by read-only transactions. (Bug #16310467)
* InnoDB: The InnoDB page-splitting algorithm could recurse
excessivly. (Bug #16345265)
* InnoDB: For debug builds, InnoDB status exporting was subject
to a race condition that could cause a server exit. (Bug
#16292043)
* InnoDB: When using ALTER TABLE to set an AUTO_INCREMENT column
value to a user-specified value, InnoDB would set the
AUTO_INCREMENT value to the user-specified value even when the
AUTO_INCREMENT value is greater than the user-specified value.
This fix ensures that the AUTO_INCREMENT value is set to the
maximum of the user-specified value and
MAX(auto_increment_column)+1, which is the expected behaviour.
(Bug #16310273)
* InnoDB: Importing a tablespace with the configuration file
present would not import the data file. This problem would
occur when all pages are not flushed from the buffer pool
after a table is altered using the copy and rename approach.
This fix ensures that all pages are flushed from the buffer
pool when a table is altered using the copy and rename
approach. (Bug #16318052)
* InnoDB: The lock_validate function, which is only present in
debug builds, acquired and released mutexes to avoid hogging
them. This behavior introduced a window wherein changes to the
hash table could occur while code traversed the same set of
data. This fix updates lock_validate logic to collect all
records for which locks must be validated, releases mutexes,
and runs a loop to validate record locks. (Bug #16235056)
* InnoDB: ALTER TABLE functions would perform a check to see if
InnoDB is in read-only mode (srv_read_only_mode=true). If
InnoDB was in read-only mode, the check would return a
successful status and do nothing else. This fix replaces
srv_read_only_mode check conditions with debug assertions.
(Bug #16227539)
* InnoDB: An improper call to abort() by InnoDB could result in
a server exit. (Bug #16263506)
* InnoDB: When the InnoDB buffer pool is almost filled with 4KB
compressed pages, inserting into 16KB compact tables would
cause 8KB pages_free to increase, which could potentially slow
or stall inserts. (Bug #16223169)
* InnoDB: An assertion failure would occur in heap->magic_n ==
MEM_BLOCK_MAGIC_N due to a race condition that appeared when
row_merge_read_clustered_index() returned an error. (Bug
#16275237)
* InnoDB: This fix removes an unnecessary debug assertion
related to page_hash locks which only affects debug builds.
The debug assertion is no longer valid and should have been
removed when hash_lock array was introduced in MySQL 5.6. (Bug
#16263167)
* InnoDB: Without warning, InnoDB would silently set
innodb-buffer-pool-instances to 1 if the buffer pool size is
less than 1GB. For example, if innodb-buffer-pool-size is set
to 200M and innodb-buffer-pool-instances is set to 4, InnoDB
would silently set innodb-buffer-pool-instances to 1. This fix
implements a warning message and new logic for
innodb-buffer-pool-size and innodb-buffer-pool-instances. (Bug
#16249500, Bug #61239)
* InnoDB: When the primary key of a table includes a column
prefix, and a full-text index is defined on the table, a
full-text search resulted in an unnecessary warning being
written to the error log. This fix suppresses the unnecessary
warning. (Bug #16169411)
* InnoDB: When InnoDB locking code was revised, a call to
register lock waits was inadvertently removed. This fix adds
the call back to the InnoDB locking code. (Bug #16208201)
* InnoDB: A direct call to the trx_start_if_not_started_xa_low()
function would cause a debug assertion. (Bug #16178995)
* InnoDB: In the case of LOCK WAIT for an insert in a foreign
key table, InnoDB could report a false dictionary-changed
error and cause the insert to fail rather than being retried.
(Bug #16174255)
* InnoDB: In some cases, deadlock detection did not work,
resulting in sessions hanging waiting for a lock-wait timeout.
(Bug #16169638)
* InnoDB: An in-place ALTER TABLE on an InnoDB table could fail
to delete the statistics for the old primary key from the
mysql.innodb_index_stats table. (Bug #16170451)
* InnoDB: This fix updates InnoDB code in ha_innodb.cc and
handler0alter.cc to use TABLE::key_info instead of both
TABLE::key_info and TABLE_SHARE::key_info. (Bug #16215361)
* InnoDB: Arithmetic underflow during page compression for
CREATE TABLE on an InnoDB table could cause a server exit.
(Bug #16089381)
* InnoDB: LOCK_TIME would not be logged correctly in the slow
query log. LOCK_TIME did not account for InnoDB row lock wait
time. (Bug #16097753)
* InnoDB: For debug builds, online ALTER TABLE operations for
InnoDB tables could cause a server exit during table
rebuilding. (Bug #16063835)
* InnoDB: In some cases, the InnoDB purge coordinator did not
use all available purge threads, resulting in suboptimal purge
activity. (Bug #16037372)
* InnoDB: ALTER TABLE for InnoDB tables was not fully atomic.
(Bug #15989081)
* InnoDB: This fix replaces most uses of UT_SORT_FUNCTION_BODY,
an InnoDB recursive merge sort, with the std::sort() function
from the C++ Standard Template Library (STL). The std::sort()
function requires less memory and is faster due to in-line
execution. (Bug #15920744)
* InnoDB: This fix implements a 256-byte boundary for extending
a VARCHAR column instead of 256-character boundary. This
change allows for in-place extension of a VARCHAR column
through an update of the data dictionary. (Bug #15863023)
* InnoDB: This fix addresses unnecessary buffer pool lookups
that would occur while freeing blob pages, and implements a
debug status instrument, innodb_ahi_drop_lookups, for testing
purposes. (Bug #15866009)
* InnoDB: Due to a resource related bug, creating numerous
tables that have a simple a full-text search index would cause
excessive memory usage. This fix adds a global configuration
parameter to limit the total memory size that full-text search
indexes can use. If the global memory limit is reached by an
index operation, a force sync is triggered. (Bug #14834698)
* InnoDB: This fix modifies InnoDB code to ensure that unused
thread handles are closed when the thread exits, instead of
leaving thread handles open until shutdown of mysqld on
Windows. (Bug #14762796)
* InnoDB: This fix removes unnecessary overhead by removing
table locking and disabling read view creation and MVCC when
InnoDB is started in read-only mode (--innodb-read-only=true).
(Bug #14729365)
* InnoDB: An error at the filesystem level, such as too many
open files, could cause an unhandled error during an ALTER
TABLE operation. The error could be accompanied by Valgrind
warnings, and by this assertion message:
Assertion `! is_set()' failed.
mysqld got signal 6 ;
(Bug #14628410, Bug #16000909)
* InnoDB: The INNODB_SYNC_ARRAY_SIZE variable was incorrectly
allowed to be configured at runtime. As documented,
INNODB_SYNC_ARRAY_SIZE must be configured when the MySQL
instance is starting up, and cannot be changed afterward. This
fix changes INNODB_SYNC_ARRAY_SIZE to a non-dynamic variable,
as intended. (Bug #14629979)
* InnoDB: The server could exit during an attempt by InnoDB to
reorganize or compress a compressed secondary index page. (Bug
#14606334)
* InnoDB: A DML operation performed while a RENAME TABLE
operation waits for pending I/O operations on the tablespace
to complete would result in a deadlock. (Bug #14556349)
* InnoDB: Attempting to unninstall the InnoDB memcached Plugin
while the plugin is still installing caused the Mysql server
to terminate. While the plugin deamon thread was still
initializing, plugin variables were not yet set and the
uninstall process could not cleanup resources. This fix adds a
variable to indicate initialization status. If initialization
is incomplete, the uninstall process will wait. (Bug
#14279541)
* InnoDB: If the value of innodb_force_recovery was less than 6,
opening a corrupted table might loop forever if a corrupted
page was read when calculating statistics for the table.
Information about the corrupted page was written repeatedly to
the error log, possibly causing a disk space issue. The fix
causes the server to halt after a fixed number of failed
attempts to read the page. To troubleshoot such a corruption
issue, set innodb_force_recovery=6 and restart. (Bug
#14147491, Bug #65469)
* InnoDB: When printing out long semaphore wait diagnostics,
sync_array_cell_print() ran into a segmentation violation
(SEGV) caused by a race condition. This fix addresses the race
condition by allowing the cell to be freed while it is being
printed. (Bug #13997024)
* InnoDB: Killing a query caused an InnoDB assertion failure
when the same table (cursor) instance was used again. This is
the result of a regression error introduced by the fix for
Bug#14704286. The fix introduced a check to handle kill
signals for long running queries but the cursor was not
restored to the proper state. (Bug #68051, Bug #16088883)
* InnoDB: On startup, InnoDB reported a message on 64-bit Linux
and 64-bit Windows systems stating that the CPU does not
support crc32 instructions. On Windows, InnoDB does not use
crc32 instructions even if supported by the CPU. This fix
revises the wording of the message and implements a check for
availability of crc32 instructions. (Bug #68035, Bug
#16075806)
* InnoDB: The length of internally generated foreign key names
was not checked. If internally generated foreign key names
were over the 64 character limit, this resulted in invalid DDL
from SHOW CREATE TABLE. This fix checks the length of
internally generated foreign key names and reports an error
message if the limit is exceeded. (Bug #44541, Bug #11753153)
* InnoDB: This fix removes left-over prototype code for
srv_parse_log_group_home_dirs, and related header comments.
(Bug #68133, Bug #16198764)
* InnoDB: Attempting to replace the default InnoDB FTS stopword
list by creating an InnoDB table with the same structure as
INFORMATION_SCHEMA.innodb_ft_default_stopword would result in
an error. SHOW CREATE TABLE revealed that the new InnoDB table
was created with CHARSET=utf8. The InnoDB FTS stopword table
validity check only supported latin1. This fix extends the
validity check for all supported character sets. (Bug #68450,
Bug #16373868)
* Partitioning: A query on a table partitioned by range and
using TO_DAYS() as a partitioing function always included the
first partition of the table when pruning. This happened
regardless of the range employed in the BETWEEN clause of such
a query. (Bug #15843818, Bug #49754)
* Partitioning: Partition pruning is now enabled for tables
using a storage engine that provides automatic partitioning,
such as the NDB storage engine, but which are explicitly
partitioned. Previously, pruning was disabled for all tables
using such a storage engine, whether or not the tables had
explicitly defined partitions.
In addition, as part of this fix, explicit partition selection
is now disabled for tables using a storage engine (such as
NDB) that provides automatic partitioning. (Bug #14827952)
References: See also Bug #14672885.
* Partitioning: Execution of ALTER TABLE ... DROP PARTITION
against a view caused the server to crash, rather than fail
with an error as expected. (Bug #14653504)
* Partitioning: A query result was not sorted if both DISTINCT
and ORDER BY were used and the underlying table was
partitioned. (Bug #14058167)
* Partitioning: Inserting any number of rows into an ARCHIVE
table that used more than 1000 partitions and then attempting
to drop the table caused the MySQL Server to fail. (Bug
#13819630, Bug #64580)
* Replication; Linux; Microsoft Windows: Replication failed
between a Linux master using lower_case_table_names set to 0
and a Windows slave having lower_case_table_names set to 2,
after a replicated table was opened on the slave; in addition,
FLUSH TABLES was required afterwards to see which updates had
actually been applied on the slave. This was because
lower_case_table_names was checked only to see whether it was
equal to 1 prior to forcing a conversion of replicated
database object names to lower case for checking the table
cache. Now in such cases, lower_case_table_names is checked to
see whether it is set to a nonzero value. (Bug #16061982)
* Replication: When using GTIDs and binary log auto-positioning,
the master had to scan all binary logs whenever the slave
reconnected (due to reasons such as I/O thread failure or a
change of master) before it could send any events to slave.
Now, the master starts from the oldest binary log that
contains any GTID not found on the slave. (Bug #16340322, Bug
#68386)
* Replication: When the server version of the master was greater
than or equal to 10, replication to a slave having a lower
server version failed. (Bug #16237051, Bug #68187)
* Replication: When replicating to a MySQL 5.6 master to an
older slave, Error 1193 (ER_UNKNOWN_SYSTEM_VARIABLE) was
logged with a message such as Unknown system variable
'SERVER_UUID' on master, maybe it is a *VERY OLD MASTER*. This
message has been improved to include more information, similar
to this one: Unknown system variable 'SERVER_UUID' on master.
A probable cause is that the variable is not supported on the
master (version: 5.5.31), even though it is on the slave
(version: 5.6.11). (Bug #16216404, Bug #68164)
* Replication: A zero-length name for a user variable (such as
@``) was incorrectly considered to be a sign of data or
network corruption when reading from the binary log. (Bug
#16200555, Bug #68135)
* Replication: Running SHOW RELAYLOG EVENTS at a slave where no
relay log file is present returned the following incorrect
error message: "Error when executing command SHOW BINLOG
EVENTS: Could not find target log." The error message text has
been changed to: "Error when executing command SHOW RELAYLOG
EVENTS: Could not find target log." (Bug #16191895)
* Replication: When MTS is on and transactions are being
applied, the slave coordinator would hang when encountering a
checksum error on a transaction event. This was due to a
deadlock situation in which the coordinator assumed a normal
stop while a worker waited for the coordinator to dispatch
more events. For debug builds, the problem appeared as an
assertion failure, which was due to the coordinator not
setting thd->is_error() when encountering an error. (Bug
#16210351)
* Replication: The print format specifier for the server_id was
incorrectly defined as a signed 32-bit integer with a range of
-2144783647 to 2144783648. This fix changes the server_id
integer type to an unsigned 32-bit integer type, with a range
of 0 to 4294967295, which is the documented range for the
--server-id option. (Bug #16210894)
* Replication: mysqlbinlog can connect to a remote server and
read its binary logs. In MySQL 5.6 and later, this tool can
also wait for the server to generate and send additional
events, in practice behaving like a slave connecting to a
master. In cases where the server sent a heartbeat,
mysqlbinlog was unable to handle it properly. As a
consequence, mysqlbinlog failed at this point, without reading
any more events from the server. To fix this problem,
mysqlbinlog now ignores any binary log events of type
HEARTBEAT_LOG_EVENT that it receives. (Bug #16104206)
* Replication: STOP SLAVE could cause a deadlock when issued
concurrently with a statement such as SHOW STATUS that
retrieved the values for one or more of the status variables
Slave_retried_transactions, Slave_heartbeat_period,
Slave_received_heartbeats, Slave_last_heartbeat, or
Slave_running. (Bug #16088188, Bug #67545)
References: See also Bug #16088114.
* Replication: Using the --replicate-* options (see Replication
Slave Options and Variables
(http://dev.mysql.com/doc/refman/5.7/en/replication-options-sl
ave.html)) could in some cases lead to a memory leak on the
slave. (Bug #16056813, Bug #67983)
* Replication: Backtick (`) characters were not always handled
correctly in internally generated SQL statements, which could
sometimes lead to errors on the slave. (Bug #16084594, Bug
#68045)
References: This bug is a regression of Bug #14548159, Bug
#66550.
* Replication: The session-level value for gtid_next was
incorrectly reset on the slave for all rollbacks, which meant
that GTIDs could be lost for multi-statement transactions,
causing the slave to stop with an
ER_GTID_NEXT_TYPE_UNDEFINED_GROUP error. Now this is done only
when a complete transaction is being rolled back, or when
autocommit is enabled. (Bug #16084206)
* Replication: In order to provision or to restore a server
using GTIDs, it is possible to set gtid_purged to a given GTID
set listing the transactions that were imported. This
operation requires that the global gtid_executed and
gtid_purged server system variables are empty. (This is done
in order to avoid the possibility of overriding
server-generated GTIDs.)
The error message GTID_PURGED can only be set when
GTID_EXECUTED is empty that was raised when this requirement
was not met could be confusing or misleading because it did
not specify the scope of the affected variables. To prevent
this from happening, error messages that refer to variables
relating to GTIDs now specify the scope of any such variables
* Replication: In certain cases, the dump thread could send a
heartbeat out of synchronisation with format description
events. One of the effects of this issue what that, after
provisioning a new server from a backup data directory and
setting --gtid-mode=ON and enabling autopositioning (see
CHANGE MASTER TO Syntax
(http://dev.mysql.com/doc/refman/5.7/en/change-master-to.html)
), replication failed to start, with the error Read invalid
event from master.... The same problem could also cause
GTID-based replication to fail due to skipped events following
a unplanned shutdown of the master. (Bug #16051857)
* Replication: In some cases, when the slave could not recognize
the server version of the master, this could cause the slave
to fail. (Bug #16056365)
* Replication: Dropping a table that includes non-regular ASCII
characters in the table name caused a replication failure. The
parser converted the table name into standard charset
characters and stored the table name in the table_name
variable. When the drop table query was regenerated using the
table_name variable, the table name was not converted back to
the original charset.
Additionally, table and database names with 64 characters
caused an assert failure. The assert required the table or
database name to be less than 128 characters. Latin characters
require two-bytes each, which requires an assert condition of
less than or equal to 128 bits.
The fix includes a new function to convert tables names back
to the original charset, and a correction to the assert
condition allowing table and database names be less than or
equal to 128 bits. (Bug #16066637)
* Replication: When using GTID-based replication, and whenever a
transaction was executed on the master but was not sent to the
slave because the slave already had a transaction with that
ID, semisynchrononous replication timed out. One case in which
this could happen was during a failover operation where the
new master started behind the new slave. (Bug #15985893)
* Replication: An unnecessary flush to disk performed after
every transaction when using FILE as the replication info
repository type could degrade performance. Now this is done
only when both data and relay log info is stored in
(transactional) tables. (Bug #15980626)
* Replication: When reading row log events from the binary log,
the slave assumed that these events were always valid; because
of this, an event having an invalid binary log offset could
cause the slave to crash. Now in such cases, the slave fails
gracefully, and an error is reported, if any of the fields in
a given row event are invalid. (Bug #15829568)
* Replication: Table IDs used in replication were defined as
type ulong on the master and uint on the slave. In addition,
the maximum value for table IDs in binary log events is 6
bytes (281474976710655). This combination of factors led to
the following issues:
+ Data could be lost on the slave when a table was assigned
an ID greater than uint.
+ Table IDs greater than 281474976710655 were written to
the binary log as 281474976710655.
+ This led to a stopped slave when the slave encountered
two tables having the same table ID.
To fix these problems, IDs are now defined by both master and
slave as type ulonglong but constrained to a range of 0 to
281474976710655, restarting from 0 when it exceeds this value.
(Bug #14801955, Bug #67352)
* Replication: MASTER_POS_WAIT() could hang or return -1 due to
invalid updates by the slave SQL thread when transactions were
skipped by the GTID protocol. (Bug #14737388)
References: See also Bug #15927032.
* Replication: Trying to execute a Stop event on a multithreaded
slave could cause unwanted updates to the relay log, leading
the slave to lose synchronization with the master. (Bug
#14737388)
* Replication: Internal objects used for relay log information
were only partially deleted before freeing their memory. (Bug
#14677824)
* Replication: When the server starts, it checks whether
semisynchronous replication has been enabled without a lock,
and, if so, it takes the lock, then tests again. Disabling
semisynchronous replication following the first of the these
tests, but prior to the second one, could lead to a crash of
the server. (Bug #14511533, Bug #66411)
* Replication: It was possible in certain cases---immediately
after detecting an EOF in the dump thread read event loop, and
before deciding whether to change to a new binary log
file---for new events to be written to the binary log before
this decision was made. If log rotation occurred at this time,
any events that occurred following EOF detection were dropped,
resulting in loss of data. Now in such cases, steps are taken
to make sure that all events are processed before allowing the
log rotation to take place. (Bug #13545447, Bug #67929)
References: See also Bug #16016886.
* Replication: It was possible for the MASTER_POS_WAIT()
function to return prematurely following a CHANGE MASTER TO
statement that updated the RELAY_LOG_POS or RELAY_LOG_NAME.
This could happen because CHANGE MASTER TO did not update the
master log position in such cases, causing MASTER_POS_WAIT()
to read an invalid log position and to return immediately.
To fix this problem, the master log position is flagged as
invalid until the position is set to a valid value when the
SQL thread reads the first event, after which it is flagged as
valid. Functions such as MASTER_POS_WAIT() now defer any
comparison with the master log position until a valid value
can be obtained (that is, after the first event following the
CHANGE MASTER TO statement has been applied). (Bug #11766010,
Bug #59037)
* Replication: If the disk becomes full while writing to the
binary log, the server hangs until space is freed up manually.
It was possible after this was done for the MySQL server to
fail, due to an internal status value being set when not
needed. Now in such cases, rather than trying to set this
status, a warning is written in the error log instead. (Bug
#11753923, Bug #45449)
* Replication: The binary log and relay log files used the name
of the PID file instead of the host name as the basename. (Bug
#11753843, Bug #45359)
* Microsoft Windows: In Shared Memory mode
(http://dev.mysql.com/doc/refman/5.7/en/server-options.html#op
tion_mysqld_shared-memory), the MySQL Server could crash when
receiving requests from multiple threads. (Bug #13934876)
* Windows MSI installers for MySQL 5.7 had a 5.6 upgrade code,
not a 5.7 upgrade code. (Bug #16445344)
* SHOW ENGINE PERFORMANCE_SCHEMA STATUS could report incorrect
memory-allocation values when the correct values exceeded 4GB.
(Bug #16414644)
* Performance Schema statement tokenization overhead was
reduced. (Bug #16382260)
* A long database name in a GRANT statement could cause the
server to exit. (Bug #16372927)
* The server could exit if a prepared statement attempted to
create a table using the name of an existing view while an SQL
handler was opened. (Bug #16385711)
* For debug builds, checking of password constraints could raise
an assertion for statements that updated passwords. (Bug
#16289303)
* The BUILD-CMAKE file in MySQL distributions was updated with
the correct URL for CMake information. (Bug #16328024)
* A Valgrind failure could occur if a CREATE USER statement was
logged to the general query log and the old_passwords system
variable was set to 2. (Bug #16300620)
* The optimizer's attempt to remove redundant subquery clauses
raised an assertion when executing a prepared statement with a
subquery in the ON clause of a join in a subquery. (Bug
#16318585)
References: This bug is a regression of Bug #15875919.
* Very small join_buffer_size values could cause an assertion to
be raised. (Bug #16328373)
* Some aggregate queries attempted to allocate excessive memory.
(Bug #16343992)
* Incorrect results were returned if a query contained a
subquery in an IN clause which contained an XOR operation in
the WHERE clause. (Bug #16311231)
* For debug builds, an assertion could be raised if a statement
failed with autocommit enabled just before an XA START
statement was issued. (Bug #16341673)
* Conversion of numeric values to BIT could yield unexpected
results. (Bug #16271540)
* Certain legal HAVING clauses were rejected as invalid. (Bug
#16221433)
* Fixed warnings when compiling with XCode 4.6. Fixed warnings
when compiling when the _XOPEN_SOURCE or isoctal macro was
already defined in the environment. (Bug #16265300, Bug
#60911, Bug #12407384)
* Queries using range predicates that were evaluated using the
LooseScan semi-join strategy could return duplicate rows. (Bug
#16221623)
References: This bug is a regression of Bug #14728469.
* For upgrade operations, RPM packages produced unnecessary
errors about being unable to access .err files. (Bug
#16235828)
* In the range optimizer, an index merge failure could cause a
server exit. (Bug #16241773)
* For debug builds, the server could exit due to incorrect
calculation of applicable indexes for a join that involved
const tables. (Bug #16165832)
* The Performance Schema could return incorrect values for the
PROCESSLIST_INFO column of the threads table. (Bug #16215165)
* Invocation of the range optimizer for a NULL select caused the
server to exit. (Bug #16192219)
* mysql_config --libs displayed incorrect output. (Bug
#16200717)
* For a CREATE TABLE (... col_name TIMESTAMP DEFAULT
CURRENT_TIMESTAMP ...) ... SELECT statement for which the
SELECT did not provide a value for the TIMESTAMP column, that
column was set to '0000-00-00 00:00:00', not the current
timestamp. (Bug #16163936)
* yaSSL did not perform proper padding checks, but instead
examined only the last byte of plaintext and used it to
determine how many bytes to remove. (Bug #16218104)
* Using GROUP BY WITH ROLLUP in a prepared statement could cause
the server to exit. (Bug #16163596)
* References to the unused SIGNAL_WITH_VIO_SHUTDOWN macro in the
CMake files were removed. (Bug #16066150)
* Setting the slave_rows_search_algorithms system variable to an
inappropriate value could cause the server to exit. (Bug
#16074161)
* Directory name manipulation could result in stack overflow on
Mac OS X and Windows. (Bug #16066243)
* For debug builds, if the server was started with binary
logging disabled, executing SHOW RELAYLOG EVENTS from within a
stored procedure raised an assertion. (Bug #16043173)
* The query parser leaked memory for some syntax errors. (Bug
#16040022)
* With the thread pool plugin enabled, large numbers of
connections could lead to a Valgrind panic or failure of
clients to be able to connect. (Bug #16088658, Bug #16196591)
* The server executed EXPLAIN FORMAT=JSON for some malformed
queries improperly. (Bug #16078557)
* Performance Schema instrumentation was missing for slave
worker threads. (Bug #16083949)
* If the error for a failed CACHE INDEX statement index within a
stored program was processed by a condition handler, a
malformed packet and "Command out of sync" error occurred.
(Bug #16076180)
* The initial test database contained a dummy.bak file that
prevented DROP DATABASE from working. This file is no longer
included. Also, a db.opt file is now included that contains
these lines:
default-character-set=latin1
default-collation=latin1_swedish_ci
(Bug #16062056)
* Setting a system variable to DEFAULT could cause the server to
exit. (Bug #16044655)
* SET PASSWORD and GRANT ... IDENTIFIED BY have no effect on the
password of a user who is authenticated using an
authentication plugin that accesses passwords stored
externally to the mysql.user table. But attempts to change the
password of such a user produced no warning, leading to the
impression that the password had been changed when it was not.
Now MySQL issues an ER_SET_PASSWORD_AUTH_PLUGIN warning to
indicate that the attempt was ignored. (Bug #16072004)
* For debug builds, creating an InnoDB table in strict SQL mode
that violated the maximum key length limit caused the server
to exit. (Bug #16035659)
* Issuing a PREPARE statement using certain combinations of
stored functions and user variables caused the server to exit.
(Bug #16056537)
* Instances of #ifdef WITH_MYISAMMRG_STORAGE_ENGINE and #ifdef
WITH_CSV_STORAGE_ENGINE in the server source code were removed
because the CSV and MERGE storage engine plugins are
mandatory. (Bug #15997345)
* A mysys library string-formatting routine could mishandle
width specifiers. (Bug #15960005)
* The --character-set-server option could set connection
character set system variables to values such as ucs2 that are
not permitted. (Bug #15985752)
* During shutdown, the server could attempt to lock an
uninitialized mutex. (Bug #16016493)
* The --default-authentication-plugin option permitted invalid
plugin values, and did not always set the old_passwords system
variable to a value appropriate for the named plugin. (Bug
#16014394)
* For debug builds, executing a statement within a trigger or
stored function that caused an implicit commit raised an
assertion. (Bug #15985318)
* Under some circumstances, mysql --secure-auth permitted
passwords to be sent to the server using the old (pre-4.1)
hashing format. (Bug #15977433)
* With index condition pushdown enabled, queries for which the
pushed-down condition contained no columns in the used index
could be slow. (Bug #15896009)
* Table creation operations added entries to the Performance
Schema file_instances table, but these were not always removed
for table drop operations. (Bug #15927620)
* In special cases, the optimizer did not consider indexes that
were applicable to query processing, resulting in potentially
suboptimal execution and incorrect EXPLAIN output. (Bug
#15849135, Bug #16094171)
* A query with an EXISTS/IN/ALL/ANY subquery with an ORDER BY
clause ordering by an outer column of type BLOB that is not in
the select list caused an assertion to fire. (Bug #15875919)
References: See also Bug #14728142.
* Queries in the query cache involving a given table were
incorrectly invalidated if a TEMPORARY table of the same name
was dropped. (Bug #14839743)
* The optimizer could return nonmatching records for queries
that used ref access on string data types. (Bug #14826522)
References: See also Bug #14682735.
* Failure of CREATE SERVER due to a missing or read-only
mysql.servers table resulted in a memory leak. (Bug #14781478)
* Enabling the query cache during high client contention could
cause the server to exit. (Bug #14727815)
* Table names can be up to 64 characters, but the message string
for the ER_TABLE_NEEDS_REBUILD and ER_TABLE_NEEDS_UPGRADE
errors were truncating names longer than 32 characters. (Bug
#14753226)
* Enabling the slow query log at runtime when access permissions
on the log file prevented the server from writing to it caused
the server to exit. (Bug #14711347)
* Table removal could fail and cause the server to exit for very
long file names. (Bug #14581920)
* The server sometimes failed to respect
MAX_CONNECTIONS_PER_HOUR limits on user connections. (Bug
#14627287)
* The server could access the DEBUG_SYNC facility while closing
temporary tables during connection shutdown, after the
facility had been cleaned up, leading to an assertion being
raised. (Bug #14626800)
* The optimizer could return incorrect results after
transforming an IN subquery with aggregate functions to an
EXISTS subquery. (Bug #14586710)
* If the optimizer calculated a row count of zero for the inner
table of an outer join, it could not determine proper ordering
for the following tables. (Bug #14628746)
* When a client program loses the connection to the MySQL server
or if the server begins a shutdown after the client has
executed mysql_stmt_prepare(), the next mysql_stmt_prepare()
returns an error (as expected) but subsequent
mysql_stmt_execute() calls crash the client. (Bug #14553380)
* Previously, if multiple --login-path options were given,
mysql_config_editor ignored all but the last one. Now multiple
--login-path options result in an error. (Bug #14551712)
* If MySQL server was started with options to enable the general
query log or slow query log, but access permissions on the log
file prevented the server from writing to it, the server
started with an error message indicating that logging was off
and that the server needed to be restarted after the problem
was corrected. This was incorrect because it is also possible
to set the logging variables again at runtime (without a
restart) after correcting the problem. The error message now
indicates this possibility. (Bug #14512467)
* For debug builds, creating a TEMPORARY table inside a trigger
caused the server to exit. (Bug #14493938)
* SHOW COLUMNS on a view defined as a UNION of Geometry columns
could cause the server to exit. (Bug #14362617)
* The sha256_password_private_key_path and
sha256_password_public_key_path system variables indicate key
files for the sha256_password authentication plugin, but the
server failed to properly check whether the key files were
valid. Now in the event that either key file is invalid, the
server logs an error and exits. (Bug #14360513)
* SET var_name = VALUES(col_name) could cause the server to
exit. This syntax is now prohibited because in SET context
there is no column name and the statement returns
ER_BAD_FIELD_ERROR. (Bug #14211565)
* The COM_CHANGE_USER command in the client/server protocol did
not properly use the character set number in the command
packet, leading to incorrect character set conversion of other
values in the packet. (Bug #14163155)
* If the server was started with --skip-grant-tables, the CREATE
EVENT and ALTER EVENT statements resulted in a memory leak.
(Bug #14059662)
* Invoking the FORMAT() function with a locale and a very large
number could cause the server to exit. (Bug #14040155)
* For debug builds, improper handling for AUTO_INCREMENT value
overflow could cause the server to exit. (Bug #13875572)
* Certain plugin-related conditions can make a user account
unusable:
+ The account requires an authentication plugin that is not
loaded.
+ The account requires the sha256_password authentication
plugin but the server was started with neither SSL nor
RSA enabled as required by this plugin.
The server now checks those conditions by default and produces
warnings for unusable accounts. This checking slows down
server initialization and FLUSH PRIVILEGES, so it is made
optional by means of the new validate_user_plugins system
variable. This variable is enabled by default, but if you do
not require the additional checking, you can disable it at
startup to avoid the performance decrement. (Bug #13010061,
Bug #14506305)
* Passing an unknown time zone specification to CONVERT_TZ()
resulted in a memory leak. (Bug #12347040)
* The obsolete linuxthreads.txt and glibc-2.2.5.patch files in
the Docs directory of MySQL distributions have been removed.
(Bug #11766326)
* mysql_install_db did not escape '_' in the host name for
statements written to the grant tables. (Bug #11746817)
* The server could exit if built to permit a maximum number of
indexes per table larger than 64.
In the course of fixing this problem, a -DMAX_INDEXES=N CMake
option was added to permit building the server to support a
larger maximum number of indexes per table. The default is 64.
The maximum is 255. Values smaller than 64 are ignored and the
default of 64 is used. (Bug #11761614)
* Source code in the mysys library for the my_malloc_lock and
my_free_lock memory-locking APIs was never used and has been
removed. (Bug #54662, Bug #11762107)
* mysqld_safe used the nonportable -e test construct. (Bug
#67976, Bug #16046140)
* An out-of-memory condition could occur while handling an
out-of-memory error, leading to recursion in error handling.
(Bug #49514, Bug #11757464)
* The optimizer used loose index scan for some queries for which
this access method is inapplicable. (Bug #42785, Bug
#11751794)
* If a dump file contained a view with one character set and
collation defined on a view with a different character set and
collation, attempts to restore the dump file failed with an
"illegal mix of collations" error. (Bug #65382, Bug #14117025)
* If the server failed to read errmsg.sys, it could exit with a
segmentation fault. (Bug #53393, Bug #11760944)
* The REPLACE() function produced incorrect results when a user
variable was supplied as an argument and the operation was
performed on multiple rows. (Bug #49271, Bug #11757250)
* The output for SHOW CREATE VIEW could vary depending on the
DEFINER account privileges. (Bug #34553, Bug #11747931)
* UNION type conversion could incorrectly turn unsigned values
into signed values. (Bug #49003, Bug #11757005)
* If one thread was rebuilding a result for the query cache,
other threads in the middle of using the previous result could
fail to discard the old result properly. For debug builds,
this raised an assertion. (Bug #66781, Bug #14631798)
* UNION ALL on BLOB columns could produce incorrect results.
(Bug #50136, Bug #11758009)
* View access in low memory conditions could raise a debugging
assertion. (Bug #39307, Bug #11749556)
* Attempts to create a trigger for which a trigger with the same
action time and event already existed resulted in an
ER_NOT_SUPPORTED_YET error rather than an
ER_TRG_ALREADY_EXISTS error. (Bug #67357, Bug #14801721)
* Queries with many values in a IN() clause were slow due to
inclusion of debugging code in non-debugging builds. (Bug
#68046, Bug #16078212)
References: See also Bug #58731, Bug #11765737.
* When a view definition contained a special character in the
SEPARATOR clause of the GROUP_CONCAT() aggregate function,
mysqldump created an invalid view definition that produced an
error when the dump file was reloaded. (Bug #60920, Bug
#12395512)
* Setting max_connections to a value less than the current
number of open connections caused the server to exit. (Bug
#44100, Bug #11752803)
* Some table I/O performed by the server when calling a storage
engine were missing from the statistics collected by the
Performance Schema. (Bug #68180, Bug #16222630)
* For debug builds, some queries with SELECT ... FROM DUAL
nested subqueries raised an assertion. (Bug #60305, Bug
#11827369)
* Nonspatial indexes only support exact-match lookups for
spatial columns, but the optimizer incorrectly used range
access in some cases, leading to incorrect results. (Bug
#67889, Bug #15993693)
* If mysql is built with the bundled libedit library, the
library is built as static code, to avoid linking to a
different dynamic version at runtime. Dynamic linking could
result in use of a different, incompatible version and a
segmentation fault. (Bug #68231, Bug #16296509)
* SLEEP() produced no warning or error for NULL or negative
arguments. Now it produces a warning, or an error in strict
SQL mode. (Bug #67548, Bug #15859462)
* The --log-slow-admin-statements and
--log-slow-slave-statements command options now are exposed at
runtime as the log_slow_admin_statements and
log_slow_slave_statements system variables. Their values can
be examined using SHOW VARIABLES. The variables are dynamic,
so their values can can be set at runtime. (The options were
actually replaced by the system variables, but as system
variables can be set at server startup, no option
functionality is lost.) (Bug #59860, Bug #11766693)
* For arguments with fractional seconds greater than six
decimals, SEC_TO_TIME() truncated, rather than rounding as it
should have. (Bug #68061, Bug #16093024)
* MySQL failed to build if configured with WITH_LIBWRAP enabled.
(Bug #67018, Bug #16342793)
* If the server was started without a --datadir option, SHOW
VARIABLES could show an empty value for the datadir system
variable. (Bug #60995, Bug #12546953)
* If a table had rows in the
INFORMATION_SCHEMA.INNODB_CMP_PER_INDEX table, dropping the
table did not remove those rows. (Bug #67283, Bug #14779330)
* Configuring with -DWITH_SSL=/path/to/openssl resulted in link
errors due to selection of the incorrect libcrypto. (Bug
#68277, Bug #16284051)
* ALTER TABLE tbl_name ADD COLUMN col_name TIMESTAMP DEFAULT
CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP inserted
0000-00-00 00:00:00 rather than the current timestamp if the
alteration was done in place rather than by making a table
copy. (Bug #68040, Bug #16076089)
* If the server was started with --skip-grant-tables, ALTER USER
... PASSWORD EXPIRE caused the server to exit. (Bug #68300,
Bug #16295905)
* CMake did not check whether the system zlib had certain
functions required for MySQL, resulting in build errors. Now
it checks and falls back to the bundled zlib if the functions
are missing. (Bug #65856, Bug #14300733)
* mysql_install_db did not work in Solaris 10 sparse root zones.
(Bug #68117, Bug #16197860)
* For EXPLAIN DELETE and EXPLAIN UPDATE the possible_keys column
listed all indexes, not just the applicable indexes. (Bug
#67830, Bug #15972078)
* The Perl version of mysql_install_db mishandled some error
messages. (Bug #68118, Bug #16197542)
* Handling of SQL_CALC_FOUND_ROWS in combination with ORDER BY
and LIMIT could lead to incorrect results for FOUND_ROWS().
(Bug #68458, Bug #16383173)
* The server did not enforce the port or report_port upper limit
of 65,535 and truncated larger values. (Bug #67956, Bug
#16035522)
* Adding an ORDER BY clause following an IN subquery could cause
duplicate rows to be returned. (Bug #68330, Bug #16308085)
* If INET6_NTOA() or INET6_ATON() returned NULL for a row in a
result set, following rows also returned NULL. (Bug #68454,
Bug #16373973)
* If XA support was activated by multiple storage engines, the
server would exit. (Bug #47134, Bug #11755370)
* A statement with an aggregated, nongrouped outer query and an
aggregated, nongrouped subquery in the SELECT list could
return incorrect results. (Bug #68372, Bug #16325175)
* The SQL_NO_CACHE keyword is supposed to prevent the server
from checking the query cache to see whether the query result
is already cached, and to prevent it from caching the query
result. However, the query cache check was suppressed only if
SQL_NO_CACHE was preceded and followed by space characters.
(For example, the server checked the cache if the keyword was
followed by a newline.) Now the parser requires that the
preceding and following characters be whitespace characters,
not spaces. (Bug #64164, Bug #13641256)
* With explicit_defaults_for_timestamp enabled, inserting NULL
into a TIMESTAMP NOT NULL column now produces an error (as it
already did for other NOT NULL data types), instead of
inserting the current timestamp. (Bug #68472, Bug #16394472)
* Use of KILL to kill a statement in another session could in
some cases cause that session to return an incorrect error
code. (Bug #45679, Bug #11754124)
* If a column is declared as NOT NULL, it is not permitted to
insert NULL into the column or update it to NULL. However,
this constraint was enforced even if there was a BEFORE INSERT
(or BEFORE UPDATE trigger) that set the column to a non-NULL
value. Now the constraint is checked at the end of the
statement, per the SQL standard. (Bug #6295, Bug #11744964)
* On Windows, the log_error system variable did not accurately
reflect the error log file name in some cases. For example, if
the server was started without --console or --log-error, the
default is to log to host_name.err in the data directory, but
log_error remained blank.
Now log_error should be nonblank and reflect the log file name
in all cases, on all platforms. The value is stderr if the
server does not write error messages to a file and sends them
to the console (standard error output) instead. In particular,
on Windows, --console overrides use of an error log and sends
error messages to the console, so log_error will be set to
stderr. (Bug #8307, Bug #11745049)
* Important Change: Formerly, the ExtractValue() and UpdateXML()
functions supported a maximum length of 127 characters for
XPath expressions supplied to them as arguments. This
limitation has now been removed. (Bug #13007062, Bug #62429)
* InnoDB: Creating and altering tables repeatedly would result
in a memory leak that was due to a duplicate key error. The
duplicate key error occurred because the
row_merge_build_indexes function did not call
row_fts_psort_info_destroy often enough. As full-text search
indexes were created with a unique index, the unique index
would fail due to the duplicate key error, and full-text
search build resource would not be released. (Bug #14759111)
* InnoDB: InnoDB IO threads within Performance Schema were
exposed with the following name: "io_handler_thread". This fix
implements specific keys such as io_read_handler_thread,
io_write_handler_thread, io_ibuf_handler_thread to
differentiate InnoDB IO threads within Performance Schema.
(Bug #14670810)
* InnoDB: This fix addresses an assert condition that would
occur when inserting large BLOBs into tablespaces with a 4KB
physical page size or into some compressed tables. Extents
would not be allocated soon enough for tablespaces with
smaller physical page sizes. (Bug #14520559)
* InnoDB: On Linux systems, certain I/O requests that read or
wrote fewer than the requested number of bytes could cause the
server to crash. This issue could happen more frequently with
asynchronous I/O
(http://dev.mysql.com/doc/refman/5.7/en/glossary.html#glos_asy
nchronous_io) requests. The messages did not clearly identify
what type of error occurred:
InnoDB: Operating system error number 0 in a file operation.
InnoDB: Error number 0 means 'Success'.
With this fix, MySQL retries the operation several times
before giving up. (The number of retries is defined by the
constant NUM_RETRIES_ON_PARTIAL_IO in the source code, default
value 10.) (Bug #11761646, Bug #54160)
* Partitioning: When the server is started with
--skip-partition, it should reject DDL or DML statements on
partitioned tables. However, for DROP TABLE, the server
dropped the .frm file, and for RENAME TABLE, the server
renamed the .frm file. (Bug #11763795)
* Replication: mysqlbinlog did not properly decode DECIMAL
values in a row-based binary log. This could cause invalid
values to be printed out for DECIMAL columns. (Bug #14309019)
* Replication: When using mysqlbinlog with the --verbose option
to read a binary log written by a MySQL server using row-based
or mixed-format logging, invalid SQL could be produced when
comments appeared inside BINLOG statements. One way in which
this could happen was when a function that updated data was
used within an INSERT ... SELECT statement. (Bug #12889121)
* Replication: mysql_upgrade on the master broke replication
when the slave was run with --log-output equal to FILE or
NONE. (Bug #11763447)
* 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. (Bug
#11761457, Bug #12977988, Bug #53955)
* Replication: When an error occurs in the slave SQL thread,
this causes the Slave_SQL_Error and Slave_SQL_Errno columns
from SHOW SLAVE STATUS to display the reason for the error.
The error number should be one of the usual constants ER_*
defined in sql/share/errmsg.txt, and the error message should
be the corresponding string. However, in some cases,
Slave_SQL_Errno was set to something other than an ER_*
number, and Slave_SQL_Error to a hard-coded error message
rather than a translatable string from sql/share/errmsg.txt.
Now all errors shown by SHOW SLAVE STATUS originate in
sql/share/errmsg.txt, as expected. (Bug #11760365, Bug #52768)
* Microsoft Windows: On Microsoft Windows, CMake entries for
POSIX API's not found on Microsoft Windows were added to the
CMake cache. This decreases the number of expected "Not found"
errors while compiling MySQL. (Bug #14790333)
* Microsoft Windows: On Microsoft Windows, queries referring to
a table with invalid characters would search the system for
invalid file names. The generated system error code
(ERROR_INVALID_NAME) was not recognized by MySQL, so this
unknown error would be reported to the server log as "ERRNO:
22 - INVALID ARGUMENT". MySQL now recognizes these errors and
reports them as the table does not existing, and it no longer
logs them to the server error log. (Bug #14642248)
* Microsoft Windows: On Windows, starting the server with
--log-error and --console caused the server to write to the
log file but not the console. Before MySQL 5.5.3, this
occurred only if --log-error was specified after --console.
Now, --console overrides --log-error no matter the option
order so that --console produces console output in all cases.
(Bug #14207773, Bug #65592)
* Microsoft Windows: It was possible to specify a Named Pipe
(http://dev.mysql.com/doc/refman/5.7/en/server-options.html#op
tion_mysqld_enable-named-pipe) that was already in use. This
is no longer allowed, as an error is now emitted and the
process is aborted. After mysqld.exe was started in Named Pipe
mode with a pipe name that was already used by a different
instance, neither instance was able to shut down properly when
a shutdown command was received from a TCP socket in any of
the processes. Therefore, mysqld.exe was not terminated. (Bug
#13891058, Bug #61885)
* Microsoft Windows: On Microsoft Windows, a failed API or
function call in mysqld.exe could sometimes report the error
code 22, instead of the proper error code. (Bug #11763004)
* Joins of exactly 32 tables and containing a HAVING clause
returned an empty result. (Bug #15972635)
* The parser rejected some legal UNION statements. (Bug
#14730856)
* Setting thread_cache_size to a negative value at server
startup resulted in a value of 16384 rather than 0. (Bug
#14683107)
* The return value from IS_USED_LOCK() was reported using the
wrong data type. (Bug #14575699)
* There was no warning at startup if the server was started with
an invalid query_cache_size value. (Bug #14576423)
* Activation of a stored program handler did not preserve the
current diagnostics stack. (Bug #14342913)
* In debug builds, killing a HELP statement caused an assertion
to be raised. (Bug #14221840)
* If an error occurred during evaluation of the BEFORE
expression of a PURGE BINARY LOGS BEFORE statement, the
statement did not abort as it should have and later raised an
assertion. (Bug #14215847)
* For the index merge access method, the optimizer could make a
suboptimal choice of indexes to use. (Bug #14095506)
* An assertion could be raised if the attempt to open the .frm
file for a temporary table failed. (Bug #13359247)
* If the state of the Event Scheduler was changed during server
shutdown, the server could crash. (Bug #13002460)
* When storing the definition for a view that used the UPPER()
or LOWER() function, the function call was replaced by UCASE()
or LCASE(), respectively (as shown in the output of SHOW
CREATE VIEW). This was in spite of the fact that UPPER() and
LOWER() are standard, with UCASE() and LCASE() being MySQL
synonyms for these. This made it more difficult to move
databases between MySQL and other database systems.
With this fix, calls to UPPER() and LOWER() within views are
no longer rewritten when storing their definitions; instead,
UCASE() is now rewritten as UPPER() in stored view
definitions, and LCASE() as LOWER(), which increases the
portability of the views. (Bug #12844279)
* For queries that accessed an INFORMATION_SCHEMA table in a
subquery, and attempt to lock a mutex that had already been
locked could cause a server crash. (Bug #11765744)
* The Range checked for each record optimization is now used for
conditions with outer query references. (Bug #11750963)
* An INSERT INTO ... SELECT statement that inserted no rows
unnecessarily invalidated statements in the query cache that
used the target table. (Bug #50065, Bug #11757947)
* The server refused client connections while executing FLUSH
PRIVILEGES. (Bug #63178, Bug #13418619)
* References to a stored function without a database name
qualifier while there was no default database resulted in an
ER_SP_DOES_NOT_EXIST error rather than ER_NO_DB_ERROR. (Bug
#64692, Bug #13864485)
* Concurrent inserts were blocked by selects if the inserts were
generated from within a stored procedure. (Bug #58689, Bug
#11765698)
* Concurrent execution of DROP DATABASE and any of CREATE
FUNCTION, CREATE PROCEDURE, or CREATE EVENT could be written
to the binary log in the wrong order, causing replication
failure. (Bug #65428, Bug #14127220)
* INSERT INTO ... SELECT ... ON DUPLICATE KEY UPDATE and LOAD
DATA CONCURRENT REPLACE took too weak a lock, leading to the
possibility of concurrent SELECT statements returning
inconsistent results. (Bug #38046, Bug #11749055)
* If read_only is enabled, it is still permitted to create
TEMPORARY tables. But in this case, a non-TEMPORARY table with
the same name could also be created, which should not be
permitted. (Bug #64992, Bug #13969578)
* Enabling the session value of low_priority_updates had no
effect for INSERT statements. (Bug #64892, Bug #13939940)
* An event was not dropped from the mysql.event table under
these circumstances: The event was created while the event
scheduler was enabled; the scheduler was disabled and
re-enabled; the event expiration time was reached. (Bug
#34804, Bug #11748012)
* Using ALTER TABLE to rename a table to . resulted in a table
with no name. (Bug #49636, Bug #11757569)
* SHOW CREATE VIEW failed if the tables underlying the view were
changed. (Bug #61718, Bug #12762393)
* SHOW GLOBAL STATUS caused performance problems on busy servers
due to lock contention. (Bug #42930, Bug #11751904)
* For a view defined on a UNION, the server could create an
invalid view definition. (Bug #65388, Bug #14117018)
* For queries using ref access on string data types, the ref
access condition could be evaluated again as part of the query
condition or pushed down as an index condition to the storage
engine. (Bug #66983, Bug #14682735)
* For an ALTER TABLE statement that renamed or changed the
default value of a BINARY column, the alteration was done
using a table copy and not in place. (Bug #67141, Bug
#14735373)
* A view was created with an incorrect definition if the WHERE
clause contained string literals and character_set_client and
character_set_connection were set to different character sets.
(Bug #63094, Bug #13520710)
when they do so. (Bug #16084426, Bug #68038)