Support for the
IBMDB2I storage engine has
pstack library was nonfunctional and has
been removed, along with the
option for configure. The
--enable-pstack option for
mysqld is deprecated and will be removed in
Security Fix: A security bug was fixed. (Bug #58005)
InnoDB index used by a foreign
key constraint, while
set to 0, could cause the server to crash with an assertion.
This operation now does not cause a crash. The foreign key
constraint can no longer be enforced once the associated index
is removed, so do not rely on it for referential integrity in
(Bug #11762483, Bug #55084)
InnoDB table created with
ROW_FORMAT=DYNAMIC, a query using the
READ UNCOMMITTED isolation level could cause
the server to stop with an assertion error, if
BLOB or other large columns that use off-page
storage were being inserted at the same time.
If the MySQL Server crashed immediately after creating an
InnoDB table, the server could quit with a
signal 11 during the subsequent restart. The
issue could occur if the server halted after
InnoDB created the primary index for the
table, but before the index definition was recorded in the MySQL
References: This bug is a regression of Bug #54582.
InnoDB table could be switched to
ROW_FORMAT=COMPRESSED implicitly by a
KEY_BLOCK_SIZE clause in an
ALTER TABLE statement. Now, the
row format is only switched to compressed if there is an
ROW_FORMAT=COMPRESSED clause. on the
ALTER TABLE statement.
Any valid, nondefault
takes precedence over
both are specified.
ROW_FORMAT is not specified on either the
CREATE TABLE or
TABLE statement, or is specified as
DEFAULT. In case of a conflict between
ROW_FORMAT clauses, the
KEY_BLOCK_SIZE is ignored if
innodb_strict_mode is off, and the statement
causes an error if
innodb_strict_mode is on.
KEY_BLOCK_SIZE=0 is now permitted
CREATE TABLE and
ALTER TABLE statements for
InnoDB tables, regardless of the setting of
innodb_strict_mode. The zero
value has the effect of resetting the
KEY_BLOCK_SIZE table parameter to its default
value, depending on the
as if it had not been specified. That default is 8 if
KEY_BLOCK_SIZE is not used or stored with the
As a consequence of this fix,
ROW_FORMAT=FIXED is not permitted when
innodb_strict_mode is enabled.
InnoDB startup messages now include the start
and end times for buffer pool initialization, and the total
buffer pool size.
In debug builds, an
INSERT ... ON DUPLICATE
statement on an
col_name = 0
AUTO_INCREMENT column caused
the server to crash.
TABLE statement acting on table partitions that failed
while the affected table was locked could cause the server to
Several compilation problems were fixed. (Bug #57992, Bug #57993, Bug #57994, Bug #57995, Bug #57996, Bug #57997, Bug #58057)
Queries executed using the Index Merge access method and a temporary file could return incorrect results. (Bug #56862)
Valgrind warnings about overlapping memory when double-assigning the same variable were corrected. (Bug #56138)
An error in a stored procedure could leave the session in a different default database. (Bug #54375)
Grouping by a
function result could cause a server crash or incorrect results.
Grouping by a function returning a
BLOB could cause an unexpected
“Duplicate entry” error and incorrect result.
find_files() function used by
SHOW statements performed
redundant and unnecessary memory allocation.
The Windows sample option files contained values more appropriate for Linux. (Bug #50021)