InnoDB: If the server crashed while an XA transaction was prepared but not yet committed, the transaction could remain in the system after restart, and cause a subsequent shutdown to hang. (Bug #11766513, Bug #59641)
Partitioning: When executing a row-ordered retrieval index merge, the partitioning handler used memory from that allocated for the table, rather than that allocated to the query, causing table object memory not to be freed until the table was closed. (Bug #11766249, Bug #59316)
When mysqlbinlog was invoked using
pos is a point in the binary
log past the format description log event), a spurious error of
the type shown here was generated:
malformed binlog: it does not contain any Format_description_log_event...
However, since there is nothing unsafe about not printing the format description log event, the error has been removed for this case. (Bug #12354268)
Replication: Typographical errors appeared in the text of several replication error messages. (The word “position” was misspelled as “postion”.) (Bug #11762616, Bug #55229)
Large values passed to
caused a buffer overflow and a server exit.
After the fix for Bug #11889186,
MAKEDATE() arguments with a year
part greater than 9999 raised an assertion.
An assertion could be raised due to a missing
NULL value check in
In debug builds on Solaris, an assertion was raised if a reverse
IP lookup with
MySQL did not build if configured with both
A problem introduced in MySQL 5.1.57 caused very old (MySQL 4.0) clients to be unable to connect to the server. (Bug #61222, Bug #12563279)
IF NOT EXISTS for an event that already existed and
was enabled caused multiple instances of the event to run.
(Bug #61005, Bug #12546938)
Valgrind warning for uninitialized values was corrected.
(Bug #59270, Bug #11766212)
ROUND() calculations, a
Valgrind warning for uninitialized memory was corrected.
(Bug #58937, Bug #11765923)
References: This bug is a regression of Bug #33143.
Valgrind warnings caused by comparing index values to an uninitialized field were corrected. (Bug #58705, Bug #11765713)
INFILE errors could leak I/O cache memory.
(Bug #58072, Bug #11765141)
INFILE, multibyte character sequences could be pushed
onto a stack too small to accommodate them.
(Bug #58069, Bug #11765139)
An embedded client aborted rather than issuing an error message
if it issued a
TEE command (
) and the
directory containing the file did not exist. This occurred
because the wrong error handler was called.
(Bug #57491, Bug #11764633)
ALTER EVENT could change the
(Bug #57156, Bug #11764334)
Compilation failed on AIX due to a missing
(Bug #55721, Bug #11763056)
In debug builds,
Field_new_decimal::store_value() was subject
to buffer overflows.
(Bug #55436, Bug #11762799)
On Linux, the mysql client built using the
libedit did not read
(Bug #49967, Bug #11757855)
The optimizer sometimes incorrectly processed
HAVING clauses for queries that did not also
ORDER BY clause.
(Bug #48916, Bug #11756928)
PROCEDURE ANALYSE() could leak memory for
NULL results, and could return incorrect
results if used with a
(Bug #48137, Bug #11756242)
On some platforms, the
Incorrect value: xxx for column
yyy at row zzz error produced by
INFILE could have an incorrect value of
(Bug #46895, Bug #11755168)
In MySQL 5.1 and up, if a table had triggers that used syntax supported in 5.0 but not 5.1, the table became unavailable. Now the table is marked as having broken triggers. These should be dropped and recreated manually. (Bug #45235, Bug #11753738)
An attempt to install nonexistent files during installation was corrected. (Bug #43247, Bug #11752142)
On FreeBSD 64-bit builds of the embedded server, exceptions were not prevented from propagating into the embedded application. (Bug #38965, Bug #11749418)