Functionality Added or Changed
On Solaris, mysql_config --libs now includes
so that libraries can be found at runtime.
InnoDB: A regression introduced by Bug #14329288 would result in a performance degradation when a compressed table does not fit into memory. (Bug #18124788, Bug #71436)
The maximum value for
now 1000000 microseconds. The previous maximum value (4294967295
microseconds on 32-bit and 18446744073709551615 microseconds on
64-bit) was unnecessarily large. Because the maximum value of
limited by the value set for
(when set to a non-zero value), the maximum value for
now the same as the maximum value for
InnoDB: In debug builds, creating a unique index on a binary column, with input data containing duplicate keys, would cause an assertion. (Bug #18010711)
InnoDB would fail to start when
the data file size in kilobytes by appending
K to the size value.
InnoDB: An insert buffer merge would cause an assertion error due to incorrectly handled ownership information for externally stored BLOBs.
InnoDB: Assertion failure in thread
thread_numin file ibuf0ibuf.cc line 4080 InnoDB: Failing assertion: rec_get_deleted_flag(rec, page_is_comp(page))
would have no affect on the next auto-increment value.
(Bug #14049391, Bug #65225)
Replication: The server did not handle correctly the insertion of a row larger than 4 GB when using row-based replication. (Bug #17081415)
Replication: When using row-based replication, an additional auto-increment column on the slave version of a table was not updated correctly; a zero was inserted instead. (Bug #17066269, Bug #69680)
Statements involving the Performance Schema tables should not be
written to the binary log, because the content of these tables
is applicable only to a given MySQL Server instance, and may
differ greatly between different servers in a replication
topology. The database administrator should be able to configure
DELETE) or flush
TRUNCATE TABLE) performance
schema tables on a single server without affecting others.
However, when replicating from a MySQL 5.5 master to a MySQL 5.5
or later slave, warnings about unsafe statements updating
Performance Schema tables were elevated to errors. For MySQL 5.6
and later slaves, this prevented the simultaneous use of
performance_schema and GTIDs (see
Replication with Global Transaction Identifiers, in the
MySQL 5.6 Manual).
This fix causes all updates on tables in the
performance_schema database to be filtered on
the master and not replicated, regardless of the type of logging
that is in effect. Prior to this fix, statements using were
handled by being marked as unsafe for replication, which caused
warnings during execution; the statements were nonetheless
written to the binary log, regardless of the logging format in
Existing replication behavior for tables in the
INFORMATION_SCHEMA database is not changed by
For more information, see MySQL Performance Schema. (Bug #16814264)
References: See also Bug #14741537, Bug #18259193.
Compilation failed if MySQL was configured with
CFLAGS set to include a
-Werror option with an argument.
libmysqld embedded server library
was not built on Linux.
(Bug #18123048, Bug #16430656, Bug #68559)
While printing the server version, the mysql client did not check for buffer overflow in a string variable. (Bug #18186103)
Contraction information in a collation could be mishandled, resulting in incorrect decisions about whether a character is part of a contraction, and miscalculation of contraction weights. (Bug #17760379)
Updating the Performance Schema
setup_instruments table on a
replication master caused a slave to exit.
Due to a race condition, it was possible for two threads to end up with the same query ID for different queries. (Bug #58785, Bug #11765785)
When run by
root, mysqld --help
--verbose exited with a nonzero error code after
displaying the help message.
(Bug #70058, Bug #17324415)
MySQL client programs from a Community Edition distribution
could not connect using SSL to a MySQL server from an Enterprise
Edition. This was due to a difference in certificate handling by
yaSSL and OpenSSL (used for Community and Enterprise,
respectively). OpenSSL expected a blank certificate to be sent
when not all of the
options were specified, and yaSSL did not do so. To resolve
this, yaSSL has been modified to send a blank certificate when
an option is missing.
(Bug #68788, Bug #16715064)
A deadlock error occurring during subquery execution could cause an assertion to be raised. (Bug #69969, Bug #17307201)
For system variables that take a string value,
SET statements permitted an unquoted value,
but values that contained dots were parsed incorrectly and only
part of the value was assigned. For example,
slow_query_log_file = my_slow.log assigned the value
my_slow. Now such values must be quoted or an
(Bug #69703, Bug #17075846)
On Windows, mysql_install_db.pl could be run
only from within the
bin directory under
the installation directory.
(Bug #42421, Bug #11751526)