This is a bugfix release for the current production release family.
This section documents all changes and bug fixes that have been applied since the last official MySQL release. If you would like to receive more fine-grained and personalized update alerts about fixes that are relevant to the version and features you use, please consider subscribing to MySQL Enterprise (a commercial MySQL offering). For more details, please see (http://www.mysql.com/products/enterprise).
ROUTINE_DEFINITIONcolumn now is defined as
NOT NULL. Also,
NULLrather than the empty string is returned as the column value if the user does not have sufficient privileges to see the routine definition. (Bug #20230)
innodb_log_arch_dirsystem variable (which has been unused since MySQL 4.0.6) is now deprecated and should no longer be used. It will be removed in MySQL 5.1.
Program Database (PDB) files (with file name extension
.pdb) are now included by default in Windows distributions. These can be used to help diagnose problems with mysqld and other tools. See Debugging a MySQL Server.
Security Fix: If a user has access to
t, that user can create a
t. However, if the user's privileges on
tare subsequently revoked, the user can continue to access
tby doing so through
m. If this behavior is undesirable, you can start the server with the new
--skip-mergeoption to disable the
MERGEstorage engine. (Bug #15195, CVE-2006-4031)
MySQL Cluster: The repeated creating and dropping of a table would eventually lead to
NDBError 826, Too many tables and attributes ... Insufficient space. (Bug #20847)
Replication: A race condition during slave server shutdown caused an assert failure. (Bug #20850)
Replication: With the
auto_increment_incrementsystem variable set larger than 1, if the next generated
AUTO_INCREMENTvalue would be larger than the column's maximum value, the value would be clipped down to that maximum value and inserted, even if the resulting value would not be in the generated sequence. This could cause problems for master-master replication. Now the server clips the value down to the previous value in the sequence, which correctly produces a duplicate-key error if that value already exists in the column. (Bug #20524)
Replication: If a table on a slave server had a higher
AUTO_INCREMENTcounter than the corresponding master table (even though all rows of the two tables were identical), in some cases
INSERT ... ON DUPLICATE KEY UPDATEwould not replicate properly using statement-based logging. (Different values would be inserted on the master and slave.) (Bug #20188)
Under heavy load (executing more than 1024 simultaneous complex queries), a problem in the code that handles internal temporary tables could lead to writing beyond allocated space and memory corruption.
Use of more than 1024 simultaneous cursors server wide also could lead to memory corruption. This applies to both stored procedure cursors and C API cursors. (Bug #21206)
Failure to account for a
NULLtable pointer on big-endian machines could cause a server crash during type conversion. (Bug #21135)
mysqldump sometimes did not select the correct database before trying to dump views from it, resulting in an empty result set that caused mysqldump to die with a segmentation fault. (Bug #21014)
SELECTthat used a subquery in the
FROMclause that did not select from a table failed when the subquery was used in a join. (Bug #21002)
In a view defined with
SQL SECURITY DEFINER, the
CURRENT_USER()function returned the invoker, not the definer. (Bug #20570)
SELECT @@INSERT_IDdisplayed a value unrelated to a preceding
SET INSERT_ID. (It returned
LAST_INSERT_IDinstead.) (Bug #20392)
The mysql client did not understand
helpcommands that had spaces at the end. (Bug #20328)
mysqldump produced a malformed dump file when dumping multiple databases that contained views. (Bug #20221)
INSERT ... SELECT ... JOIN ... USINGwithout qualifying the column names caused
ERROR 1052 "column 'x' in field list is ambiguous"even in cases where the column references were unambiguous. (Bug #18080)
Assignments of values to variables of type
TEXTwere handled incorrectly in stored routines. (Bug #17225)
DATA DIRECTORYtable option did not work for
TEMPORARYtables. (Bug #8706)
Bug #10952 may cause inadvertent data loss. A fix for this bug was included in MySQL 5.0.23, but the approach used caused a loss of intended functionality. Because of this, that fix has been reverted in MySQL 5.0.24. As a consequence, the risk of inadvertent data loss still exists (see Bug #10952).