This section documents all changes and bugfixes that have been applied since the last MySQL Enterprise Server and MySQL Community Server release (5.0.83). 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.
A suitable database identifier supplied to the
COM_DROP_DB command could cause a
segmentation fault, and thereby a denial of service.
(Bug #45790, CVE-2009-2446)
InnoDB adaptive hash latch is released
(if held) for several potentially long-running operations. This
improves throughput for other queries if the current query is
removing a temporary table, changing a temporary table from
memory to disk, using
CREATE TABLE ...
SELECT, or performing a
repair on a table used within a transaction.
Replication: When reading a binary log that was in use by a master or that had not been properly closed (possibly due to a crash), the following message was printed: Warning: this binlog was not closed properly. Most probably mysqld crashed writing it. This message did not take into account the possibility that the file was merely in use by the master, which caused some users concern who were not aware that this could happen.
To make this clear, the original message has been replaced with Warning: this binlog is either is use or was not closed properly. (Bug #34687)
On Windows, the
_PC macro in
my_global.h was causing problems for modern
compilers. It has been removed because it is no longer used.
Shared-memory connections did not work in Vista if mysqld was started from the command line. (Bug #41190)
Index Merge followed by a filesort could result in a server
not large enough for all sort keys.
References: See also Bug #40974.
In the mysql client, using a default
character set of
binary caused internal
commands such as
DELIMITER to become case
Valgrind warnings that occurred for
TABLE STATUS with
When invoked to start multiple server instances, mysqld_multi sometimes would fail to start them all due to not changing location into the base directory for each instance. (Bug #36654)
A workaround for a Sun Studio bug was instituted. (Bug #41710)
The mysql client could misinterpret some character sequences as commands under some circumstances. (Bug #45236)
A Valgrind error during subquery execution was corrected. (Bug #36995)
UPDATE statements that
affected no rows returned a rows-affected count of one.
Compiler warnings on Mac OS X were fixed. (Bug #45286)
Some Perl scripts in AIX packages contained an incorrect path to the perl executable. (Bug #44643)
References: See also Bug #22891.