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.91). 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.
Functionality Added or Changed
The time zone tables available at http://dev.mysql.com/downloads/timezones.html have been updated. These tables can be used on systems such as Windows or HP-UX that do not include zoneinfo files. (Bug #40230)
Security Fix: A security bug was fixed. (Bug #57952)
During evaluation of arguments to extreme-value functions such
GREATEST(), type errors did not
propagate properly, causing the server to crash.
(Bug #55826, CVE-2010-3833)
Security Fix: The server could crash after materializing a derived table that required a temporary table for grouping. (Bug #55568, CVE-2010-3834)
A user-variable assignment expression that is evaluated in a
logical expression context can be precalculated in a temporary
GROUP BY. However, when the
expression value is used after creation of the temporary table,
it was re-evaluated, not read from the table, and a server crash
(Bug #55564, CVE-2010-3835)
Joins involving a table with a unique
SET column could cause a server
(Bug #54575, CVE-2010-3677)
LIKE predicates during view
preparation could cause a server crash.
(Bug #54568, Bug #11762026, CVE-2010-3836)
ROLLUP together could cause a server crash.
(Bug #54476, CVE-2010-3837)
Queries could cause a server crash if the
LEAST() function had a mixed list
of numeric and
arguments, and the result of such a function was processed using
an intermediate temporary table.
(Bug #54461, CVE-2010-3838)
Security Fix: A security bug was fixed. (Bug #53933)
Security Fix: A security bug was fixed. (Bug #53907)
EXPLAIN with queries of the
SELECT ... UNION ... ORDER BY (SELECT ... WHERE
...) could cause a server crash.
(Bug #52711, CVE-2010-3682)
Security Fix: A security bug was fixed. (Bug #52357)
Security Fix: A security bug was fixed. (Bug #52315)
Security Fix: A security bug was fixed. (Bug #48157)
InnoDB: Creating or dropping a table with 1023 transactions active caused an assertion failure. (Bug #49238)
make_binary_distribution target to
make could fail on some platforms because the
lines generated were too long for the shell.
A client could supply data in chunks to a prepared statement
parameter other than of type
BLOB using the
API function (or
command). This led to a crash because other data types are not
valid for long data.
Builds of the embedded mysqld failed due to a
missing element of the
(Bug #53908, Bug #53912)
The definition of the
MY_INIT macro in
my_sys.h included an extraneous semicolon,
which could cause compilation failure.
mysqld could fail during execution when using SSL. (Bug #34236)
Threads that were calculating the estimated number of records
for a range scan did not respond to the
KILL statement. That is, if a
range join type is possible
(even if not selected by the optimizer as a join type of choice
and thus not shown by
the query in the
statistics state (shown by
SHOW PROCESSLIST) did not
respond to the