Functionality Added or Changed
Important Change; Replication:
DUPLICATE KEY UPDATE is now marked as unsafe for
statement-based replication if the target table has more than
one primary or unique key. For more information, see
Determination of Safe and Unsafe Statements in Binary Logging.
(Bug #58637, Bug #11765650, Bug #13038678)
Security Fix: A security bug was fixed. (Bug #64884)
When binary log statements were replayed on the slave, the
counters were incremented by
statements initiating transactions affecting
InnoDB tables but not by
COMMIT statements ending such
transactions. This affected these statements whether they were
replicated or they were run using
Running concurrent bulk inserts on a server with
greater than 1, and
could result in intermittent errors like the following, even
with the primary key set to auto_increment and omitted from the
Duplicate entry '
value' for key 'PRIMARY'
The workaround was to set
(Bug #13817703, Bug #61209)
Passing a user variable as an argument to
GROUP_CONCAT() could cause a
server exit if the variable value changed during query
--bind-address option was
given a host name value and the host name resolved to more than
one IP address, the server failed to start. For example, with
localhost resolved to both
failed. Now the server prefers the IPv4 address in such cases.
(Bug #61713, Bug #12762885)
mysql_use_result() are not for
use with prepared statements and are not intended to be called
but failed to return an error when invoked that way in
(Bug #62136, Bug #13738989)
References: See also Bug #47485.
On Windows, mysqlslap crashed for attempts to connect using shared memory. (Bug #31173, Bug #11747181, Bug #59107, Bug #11766072)