Very old (MySQL 4.0) clients are not working temporarily due to a problem discovered after the release of MySQL 5.5.12. We are looking at fixing the problem. Update: This is fixed in MySQL 5.5.14.
The client-side plugin that accompanies the server-side Windows authentication plugin is now included in all MySQL distributions. This will permit clients from any release, whether commercial or community, to connect to a server that has the server-side plugin loaded. See The Windows Native Authentication Plugin (Bug #59780, Bug #11766631)
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)
The MySQL server could hang during
OPTIMIZE TABLE, or
ALTER TABLE or other DDL operation that
performs a table copy for an
InnoDB table, if
such operations were performed by multiple sessions
simultaneously. The error was reported as:
InnoDB: Error: semaphore wait has lasted > 600 seconds
(Bug #11760042, Bug #52409)
With the setting
InnoDB tables covered by foreign
key constraints could fail after a server restart. This is a
similar problem to the foreign key error in Bug #11831040 / Bug
#60196 / Bug #60909, but with a different root cause and
occurring on Mac OS X.
did not take into account the possibility that a key
specification could be
NULL in some cases.
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)
XA COMMIT could
fail to clean up the error state if it discovered that the
current XA transaction had to be rolled back. Consequently, the
next XA transaction could raise an assertion when it checked for
proper cleanup of the previous transaction.
An internal client macro reference was removed from the
client_plugin.h header file. This reference
made the file unusable.
(Bug #60746, Bug #12325444)
For repeated invocation of some stored procedures, the server consumed memory that it did not release until the connection terminated. (Bug #60025, Bug #11848763)
The server did not check for certain invalid out of order sequences of XA statements, and these sequences raised an assertion. (Bug #59936, Bug #11766752, Bug #12348348)
With the conversion from GNU autotools to
CMake for configuring MySQL, the
USE_SYMDIR preprocessor symbol was omitted.
This caused failure of symbolic links (described at
Using Symbolic Links).
(Bug #59408, Bug #11766320)
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)
Internal Performance Schema header files were unnecessarily installed publicly. (Bug #53281)
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)
returned incorrect results when the arguments to
CONCAT() were columns with an
integer data type declared with a display width narrower than
the values in the column. (For example, if an
INT(1) column contained