MySQL Community Server 5.0.84 has been released

[sunanda menon]

Dear MySQL users,

MySQL Community Server 5.0.84, 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

http://dev.mysql.com/downloads/

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,
patches etc.:

http://forge.mysql.com/wiki/Contributing

This section documents all changes and bugfixes that have been
applied since the last MySQL Community Server release (5.0.83).

http://dev.mysql.com/doc/refman/5.0/en/news-5-0-84.html

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.


Bugs fixed:

* Important Change: Replication: BEGIN, COMMIT, and ROLLBACK
     statements are no longer affected by --replicate-do-db or
     --replicate-ignore-db rules.
     (Bug#43263: http://bugs.mysql.com/43263)

   * 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: http://bugs.mysql.com/34687)

   * The server crashed for attempts to use REPLACE or INSERT ...
     ON DUPLICATE KEY UPDATE with a view defined using a join.
     (Bug#45806: http://bugs.mysql.com/45806)

   * The combination of MIN() or MAX() in the select list with
     WHERE and GROUP BY clauses could lead to incorrect results.
     (Bug#45386: http://bugs.mysql.com/45386)

   * Use of ROUND() on a LONGTEXT or LONGBLOB column of a derived
     table could cause a server crash.
     (Bug#45152: http://bugs.mysql.com/45152)

   * Index Merge followed by a filesort could result in a server
     crash if sort_buffer_size was not large enough for all sort
     keys. (Bug#44810: http://bugs.mysql.com/44810)

   * The PASSWORD() and OLD_PASSWORD() functions could read memory
     outside of an internal buffer when used with BLOB arguments.
     (Bug#44767: http://bugs.mysql.com/44767)

   * Shared-memory connections did not work in Vista if mysqld was
     started from the command line.
     (Bug#41190: http://bugs.mysql.com/41190)

   * In the mysql client, using a default character set of binary
     caused internal commands such as DELIMITER to become case
     sensitive. (Bug#37268: http://bugs.mysql.com/37268)

   * 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. (Bug#34309: http://bugs.mysql.com/34309)

   * The InnoDB adaptive hash latch is released (if held) for
     serveral 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 MyISAM
     repair on a table used within a transaction.
     (Bug#32149: http://bugs.mysql.com/32149)


Thanks
Sunanda