This is a Service Pack release of the MySQL Enterprise Server 5.1.
Support for the
IBMDB2Istorage engine has been removed. (Bug #58079)
Incompatible Change: When
auto_increment_incrementis greater than one, values generated by a bulk insert that reaches the maximum column value could wrap around rather producing an overflow error.
As a consequence of the fix, it is no longer possible for an auto-generated value to be equal to the maximum
BIGINT UNSIGNEDvalue. 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,
EXTRACT(WEEK FROM, where
DATETIMEcolumn, is now disallowed altogether because its return value depends on the value of the
default_week_formatsystem variable. (Bug #54483, Bug #11761948)
References: See also Bug #57071, Bug #11764255.
InnoDBsystem tablespace could grow continually for a server under heavy load. (Bug #57611)
InnoDB: If the server crashed during an
ALTER TABLEoperation on an
InnoDBtable, examining the table through
SHOW CREATE TABLEor querying the
INFORMATION_SCHEMAtables could cause the server to stop with an assertion error. (Bug #56982)
ALTER TABLE ... PARTITIONstatements could cause memory leaks. (Bug #56380, Bug #11763641)
References: See also Bug #46949, Bug #11755209, Bug #56996, Bug #11764187.
MIN(could return an incorrect result in some cases. (Bug #59211, Bug #11766165)
Unnecessary subquery evaluation in contexts such as statement preparation or view creation could cause a server crash. (Bug #57703)
View creation could produce Valgrind warnings. (Bug #57352)
NULLgeometry values could cause a crash in
Item_func_spatial_collection::fix_length_and_dec. (Bug #57321)
SET GLOBAL debugcould cause a crash on Solaris if the server failed to open the trace file. (Bug #57274)
Valgrind warnings about overlapping memory when double-assigning the same variable were corrected. (Bug #56138)
On FreeBSD, if mysqld was killed with a
SIGHUPsignal, it could corrupt
.ibdfiles. (Bug #51023, Bug #11758773)