|| ||sunanda menon <Sunanda.Menon-AT-Sun.COM> |
|| ||announce-AT-lists.mysql.com, mysql-AT-lists.mysql.com, packagers-AT-lists.mysql.com |
|| ||MySQL Community Server 5.0.85 has been released |
|| ||Mon, 24 Aug 2009 15:53:47 +0530|
|| ||Article, Thread
Dear MySQL users,
MySQL Community Server 5.0.85, a new version of the popular Open Source
Database Management System, has been released. This and future releases
in the MySQL Community Server 5.0 series share version numbers with
their MySQL Enterprise Server counterparts.
The release is now available in source and binary form for a number of
platforms from our download pages at
and mirror sites. Note that not all mirror sites may be up to date at
this point in time, so if you can't find this version on some mirror,
please try again later or choose another download site.
We welcome and appreciate your feedback, bug reports, bug fixes,
Due to problems making packages for Linux IA64 compiled with icc
generic, we have decided to not continue providing the "IA64, glibc-2.3,
icc" tarballs. Note that Red Hat and SuSE specific RPMs for IA64
icc are still available.
This section documents all changes and bugfixes that have been
applied since the last MySQL Community Server release (5.0.84).
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
* The server printed warnings at startup about adjusting the
value of the max_join_size system variable. (These were
harmless, but might be seen by users as significant.)
* The server crashed if evaluation of GROUP_CONCAT(... ORDER BY)
required allocation of a sort buffer but allocation failed.
* After an error such as a table-full condition, INSERT IGNORE
could cause an assertion failure for debug builds.
* An optimization that moved an item from a subquery to an outer
query could cause a server crash.
* Several Valgrind warnings were corrected.
* For problems reading SSL files during SSL initialization, the
server wrote error messages to stderr rather than to the error
log. (Bug#45770: http://bugs.mysql.com/45770)
* The vendor name change from MySQL AB to Sun Microsystems, Inc.
in RPM packages was not handled gracefully when upgrading
MySQL using an RPM package.
* Compiler warnings on Windows were fixed.
* Invalid memory reads could occur using the compressed
* Invalid input could cause invalid memory reads by the parser.
* The server did not always check the return value of calls to
the hash_init() function.
* A test for stack growth failed on some platforms, leading to
server crashes. (Bug#42213: http://bugs.mysql.com/42213)
* SHOW PROCESSLIST could access freed memory of a stored
procedure run in a concurrent session.
* make_binary_distribution did not always generate correct
distribution names. (Bug#37808: http://bugs.mysql.com/37808)
* The server crashed when executing a prepared statement
containing a duplicated MATCH() function call in the select
list and ORDER BY clause; for example, SELECT MATCH(a)
AGAINST('test') FROM t1 ORDER BY MATCH(a) AGAINST('test').
* If InnoDB reached its limit on the number of concurrent
transactions (1023), it wrote a descriptive message to the
error log but returned a misleading error message to the
client, or an assertion failure occurred.
Database Technology Group
to post comments)