End of Product Lifecycle. Active development for MySQL Database Server version 5.0 has ended. Oracle offers various support offerings which may be of interest. For details and more information, see the MySQL section of the Lifetime Support Policy for Oracle Technology Products (http://www.oracle.com/us/support/lifetime-support/index.html). Please consider upgrading to a recent version.
This section documents all changes and bugfixes that have been applied since the last MySQL Enterprise Server and MySQL Community Server release (5.0.89). 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/advisors.html.
Security Fix: For servers built with yaSSL, a preauthorization buffer overflow could cause memory corruption or a server crash. We thank Evgeny Legerov from Intevydis for providing us with a proof-of-concept script that permitted us to reproduce this bug. (Bug #50227, CVE-2009-4484)
FLUSH LOGS did
not close and reopen the binary log index file.
References: See also Bug #34582.
Some prepared statements could raise an assertion when re-executed. (Bug #49570)
Valgrind warnings for
TABLE were corrected.
Specifying an index algorithm (such as
indexes caused a server crash. These index types do not support
algorithm specification, and it is not longer permitted to do
The optimizer sometimes incorrectly handled conditions of the
strmake() calls had an incorrect
length argument (too large by one).
On Fedora 12,
strmov() did not guarantee
correct operation for overlapping source and destination buffer.
Calls were fixed to use an overlap-safe version instead.
Incomplete reset of internal
could cause a crash with
eq_ref table access in
Re-execution of a prepared statement could cause a server crash. (Bug #48508)
The error message for
ER_UPDATE_INFO was subject to
buffer overflow or truncation.
On Solaris, the server printed no stack trace to the error log after a crash. (Bug #47391)
A crash occurred when a user variable that was assigned to a
subquery result was used as a result field in a
SELECT statement with aggregate
NULL values sometimes did not
produce a correct result.
MyISAM files were
opened, they were always memory mapped, sometimes causing
memory-swapping problems. To deal with this, a new system
myisam_mmap_size, was added to
permit limiting the amount of memory used for memory mapping of