Skip navigation links
C.1.2 Changes in MySQL 5.0.89 (02 December 2009) »
Section Navigation      [Toggle]

C.1.1. Changes in MySQL 5.0.90 (15 January 2010)

End of Product Lifecycle. Active development and support for MySQL Database Server version 5.0 has ended. However, there is still extended support available. For details, see http://www.mysql.com/about/legal/lifecycle/#calendar. According to the MySQL Lifecycle Policy (see http://www.mysql.com/about/legal/lifecycle/#policy), only Security and Severity Level 1 issues will still be fixed for MySQL 5.0. 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.

Bugs fixed:

  • 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 allowed us to reproduce this bug. (Bug#50227, CVE-2009-4484)

  • Replication: FLUSH LOGS did not actually close and reopen the binary log index file. (Bug#48738)

    See also Bug#34582.

  • Some prepared statements could raise an assertion when re-executed. (Bug#49570)

  • Valgrind warnings for CHECKSUM TABLE were corrected. (Bug#49465)

  • Specifying an index algorithm (such as BTREE) for SPATIAL or FULLTEXT indexes caused a server crash. These index types do not support algorithm specification, and it is now disallowed to do so. (Bug#49250)

  • The optimizer sometimes incorrectly handled conditions of the form WHERE col_name='const1' AND col_name='const2'. (Bug#49199)

  • Several strmake() calls had an incorrect length argument (too large by one). (Bug#48983)

  • 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. (Bug#48866)

  • Incomplete reset of internal TABLE structures could cause a crash with eq_ref table access in subqueries. (Bug#48709)

  • 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. (Bug#48500)

  • On Solaris, no stack trace was printed 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 functions. (Bug#47371)

  • Comparison with NULL values sometimes did not produce a correct result. (Bug#42760)

  • When compressed MyISAM files were opened, they were always memory mapped, sometimes causing memory-swapping problems. To deal with this, a new system variable, myisam_mmap_size, was added to limit the amount of memory used for memory mapping of MyISAM files. (Bug#37408)