Functionality Added or Changed
The time zone tables available at http://dev.mysql.com/downloads/timezones.html have been updated. These tables can be used on systems such as Windows or HP-UX that do not include zoneinfo files. (Bug #40230)
Security Fix: A security bug was fixed. (Bug #57952)
UPDATE statement for an
InnoDB table could be slower than
necessary if it changed a column covered by a prefix index, but
did not change the prefix portion of the value. The fix improves
performance for InnoDB 1.1 in MySQL 5.5 and higher, and the
InnoDB Plugin for MySQL 5.1.
(Bug #58912, Bug #11765900)
InnoDB tables in
REFERENTIAL_CONSTRAINTS were slower
than necessary because statistics were rechecked more often than
required, even more so when many foreign keys were present. The
improvement to this may be of particular benefit to users of
MySQL Enterprise Monitor with many monitored servers or tens of
thousands of tables.
(Bug #43818, Bug #11752585)
auto_increment_increment is greater than
one, values generated by a bulk insert that reaches the maximum
column value could wrap around rather producing an overflow
As a consequence of the fix, it is no longer possible for an
auto-generated value to be equal to the maximum
UNSIGNED value. It is still possible to store that
value manually, if the column can accept it.
(Bug #39828, Bug #11749800)
Important Change; Partitioning:
Date and time functions used as partitioning functions now have
the types of their operands checked; use of a value of the wrong
type is now disallowed in such cases. In addition,
col_name is a
DATETIME column, is now
disallowed altogether because its return value depends on the
value of the
(Bug #54483, Bug #11761948)
References: See also Bug #57071, Bug #11764255.
The server could crash with an assertion error, if a stored
procedure, stored function, or trigger modified one
InnoDB table containing an
column, and dropped another
table containing an auto-increment column.
InnoDB status output, the value
I/O sum could be incorrect, displayed
as a very large number.
The presence of a double quotation mark inside the
COMMENT field for a column could prevent a
foreign key constraint from being created properly.
(Bug #59197, Bug #11766154)
A compilation problem affected the
source code on NetBSD/sparc64.
References: See also Bug #53916.
... PARTITION statements could cause memory leaks.
(Bug #56380, Bug #11763641)
References: See also Bug #46949, Bug #11755209, Bug #56996, Bug #11764187.
USE statements to its output only
when the default database changed between events. To illustrate
how this could cause problems, suppose that a user issued the
following sequence of statements:
CREATE DATABASE mydb; USE mydb; CREATE TABLE mytable (
column_definitions); DROP DATABASE mydb; CREATE DATABASE mydb; USE mydb; CREATE TABLE mytable (
When played back using mysqlbinlog, the
CREATE TABLE statement
failed with Error: No Database Selected
because the second
was not played back, due to the fact that a database other than
mydb was never selected.
This fix ensures that mysqlbinlog outputs a
USE statement whenever it reads
one from the binary log.
(Bug #50914, Bug #11758677)
Replication: When closing a session that used temporary tables, binary logging could sometimes fail with a spurious Failed to write the DROP statement for temporary tables to binary log. (Bug #57288)
By default, a value is generated for an
AUTO_INCREMENT column by inserting either
NULL or 0 into the column. Setting the
SQL mode suppresses this behavior for 0, so that it occurs only
NULL is inserted into the column.
This behavior is also followed on a replication slave (by the
slave SQL thread) when applying events that have been logged on
the master using the statement-based format. However, when
applying events that had been logged using the row-based format,
ignored, which could lead to an assertion.
To fix this issue, the value of an
AUTO_INCREMENT column is no longer generated
when applying an event that was logged using the row-based row
format, as this value is already contained in the changes
applied on the slave.
BINLOG statement modified the
values of session variables, which could lead to problems with
operations such as point-in-time recovery. One such case
occurred when replaying a row-based binary log which relied on
OFF at the session level to create and populate a set
InnoDB tables having foreign key
Replication: When an error occurred in the generation of the name for a new binary log file, the error was logged but not shown to the user. (Bug #46166)
References: See also Bug #37148, Bug #11748696, Bug #40611, Bug #11750196, Bug #43929, Bug #51019.
Replication: Previously, when a statement failed with a different error on the slave than on the master, the slave SQL thread displayed a message containing:
The error message for the master error code
The master error code
The error message for the slaves error code
The slave error code
However, the slave has no information with which to fill in any print format specifiers for the master message, so it actually displayed the message format string. To make it clearer that the slave is not displaying the actual message as it appears on the master, the slave now indicates that the master part of the output is the message format, not the actual message. For example, previously the slave displayed information like this:
Error: "Query caused different errors on master and slave. Error on master: 'Duplicate entry '%-.192s' for key %d' (1062), Error on slave: 'no error' (0). Default database: 'test'. Query: 'insert into t1 values(1),(2)'" (expected different error codes on master and slave)
Now the slave displays this:
Error: "Query caused different errors on master and slave. Error on master: message format='Duplicate entry '%-.192s' for key %d' error code=1062 ; Error on slave: actual message='no error', error code=0. Default database: 'test'. Query: 'insert into t1 values(1),(2)'" (expected different error codes on master and slave)
EXPLAIN EXTENDED for a
query that would use condition pushdown could cause
mysqld to crash.
(Bug #58553, Bug #11765570)
Configuration with maintainer mode enabled resulted in errors when compiling with icc. (Bug #57991, Bug #58871)
cp1251 character set did not properly
support the Euro sign (
0x88). For example,
converting a string containing this character to
utf8 resulted in
rather than the
utf8 Euro sign.
View creation could produce Valgrind warnings. (Bug #57352)
During assignment of values to system variables, legality checks on the value range occurred too late, preventing proper error checking. (Bug #43233)
Some unsigned system variables could be displayed with negative values. (Bug #55794)
An assertion could be raised during concurrent execution of
DROP DATABASE and
REPAIR TABLE if the drop deleted
.TMD file at the same time the
repair tried to read details from the old file that was just
If a client supplied a user name longer than the maximum 16 characters permitted for names stored in the MySQL grant tables, all characters were being considered significant when checking for a match. Historically, only the first 16 characters were used for matching; this behavior was restored. (Bug #49752)
An assertion could be raised if –1 was inserted into an
AUTO_INCREMENT column by a statement writing
more than one row.
(Bug #50619, Bug #11758417)
When mysqld printed crash dump information, it incorrectly indicated that some valid pointers were invalid. (Bug #51817)
On FreeBSD, if mysqld was killed with a
SIGHUP signal, it could corrupt
(Bug #51023, Bug #11758773)
Unnecessary subquery evaluation in contexts such as statement preparation or view creation could cause a server crash. (Bug #57703)
my_tell() functions ignored the
MY_WME flag when they returned an error,
which could cause client programs to hang.
could return an incorrect result in some cases.
(Bug #59211, Bug #11766165)
max_allowed_packet was set larger than
16MB, the server failed to reject too-large packets with
“Packet too large” errors.
(Bug #58887, Bug #11765878)
NULL geometry values could cause a crash in