List:Announcements« Previous MessageNext Message »
From:Karen Langford Date:February 8 2011 5:04am
Subject:MySQL Server 5.0.92 has been released.
View as plain text  
Dear MySQL users,

MySQL Server 5.0.92, a new version of the popular Open Source Database
Management System, has been released.  Please note that the active
maintenance of 5.0 has ended, and these builds are only provided
because of the fixes to security bugs as described below.

The release is now available in source and binary form for a number of
platforms from our archive download page at

Mirror service for MySQL Server 5.0 has ended.  Also, support for some
platforms with very low demand has ended.  Please bear in mind that
MySQL 5.0 now receives extended support only, and that all active
development is happening on MySQL 5.1, 5.5, and beyond. You will find
the MySQL Lifecycle policy here:

For your own best interest, we strongly recommend all current users of
MySQL 5.0 to upgrade to MySQL 5.1.

We welcome and appreciate your feedback, bug reports, bug fixes,
patches etc:

This section documents all changes and bugfixes that have been applied
since the last MySQL 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

Changes in MySQL 5.0.92  (7 February, 2011)

Functionality added or changed:

    * The time zone tables available at have been
      updated. These tables can be used on systems such as
      Windows or HP-UX that do not include zoneinfo files.

Bugs fixed:

    * Security Fix: During evaluation of arguments to
      extreme-value functions (such as LEAST() and GREATEST()),
      type errors did not propagate properly, causing the
      server to crash.

    * Security Fix: The server could crash after materializing
      a derived table that required a temporary table for

    * Security Fix: A user-variable assignment expression that
      is evaluated in a logical expression context can be
      precalculated in a temporary table for 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 resulted.

    * Security Fix: Joins involving a table with a unique SET
      column could cause a server crash.

    * Security Fix: Pre-evaluation of LIKE predicates during
      view preparation could cause a server crash.

    * Security Fix: GROUP_CONCAT() and WITH ROLLUP together
      could cause a server crash.

    * Security Fix: Queries could cause a server crash if the
      GREATEST() or LEAST() function had a mixed list of
      numeric and LONGBLOB arguments, and the result of such a
      function was processed using an intermediate temporary

    * Security Fix: Using EXPLAIN with queries of the form
      SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...)
      could cause a server crash.

    * InnoDB Storage Engine: Creating or dropping a table with
      1023 transactions active caused an assertion failure.

    * The 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 TEXT or BLOB using
      the mysql_stmt_send_long_data() C API function (or
      COM_STMT_SEND_LONG_DATA command). This led to a crash
      because other data types are not valid for long data.

    * Builds of the embedded mysqld would fail due to a missing
      element of the struct NET.

    * The definition of the MY_INIT macro in my_sys.h included
      an extraneous semicolon, which could cause compilation

    * If the remote server for a FEDERATED table could not be
      accessed, queries for the INFORMATION_SCHEMA.TABLES table

    * mysqld could fail during execution when using SSL.

    * 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 EXPLAIN), the query in the
      statistics state (shown by the SHOW PROCESSLIST) did not
      respond to the KILL statement.

Sunanda Menon
Release Engineer, MySQL, Oracle.

MySQL Server 5.0.92 has been released.Karen Langford9 Feb