This is a Service Pack release of the MySQL Enterprise Server 5.1.
... REORGANIZE PARTITION statement on an
InnoDB table failed due to
expiring while waiting for a lock,
not clean up any temporary files or tables which it had created.
Attempting to reissue the
TABLE statement following the timeout could lead to
storage engine errors, or possibly a crash of the server.
set to 4 or higher, the server could crash when opening an
InnoDB table containing an
auto-increment column. MySQL versions 5.1.31 and later were
Referring to a subquery result in a
clause could produce incorrect results.
filesort sorting method applied to a
CHAR(0) column could lead to a
In some cases a subquery need not be evaluated because it returns only aggregate values that can be calculated from table metadata. This sometimes was not handled by the enclosing subquery, resulting in a server crash. (Bug #49512)
flush_cache_records() did not correctly check
for errors that should cause statement execution to stop,
leading to a server crash.