Documentation Home
MySQL 5.0 Release Notes
Related Documentation Download these Release Notes
PDF (US Ltr) - 2.1Mb
PDF (A4) - 2.1Mb
EPUB - 0.6Mb

MySQL 5.0 Release Notes  /  Changes in MySQL 5.0.83 (2009-05-29)

Changes in MySQL 5.0.83 (2009-05-29)

This section documents all changes and bugfixes that have been applied since the last MySQL Enterprise Server and MySQL Community Server release (5.0.82). 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

Functionality Added or Changed

Bugs Fixed

  • Replication: When stopping and restarting the slave while it was replicating temporary tables, the slave server could crash or raise an assertion failure. This was due to the fact that, although temporary tables were saved between slave thread restarts, the reference to the thread being used (table->in_use) was not being properly updated when restarting, continuing to reference the old thread instead of the new one. This issue affected statement-based replication only. (Bug #41725)

  • UNCOMPRESSED_LENGTH() returned a garbage result when passed a string shorter than 5 bytes. Now UNCOMPRESSED_LENGTH() returns NULL and generates a warning. (Bug #44796)

  • Several Valgrind warnings were silenced. (Bug #44774, Bug #44792)

  • Incorrect time was reported at the end of mysqldump output. (Bug #44424)

  • EXPLAIN EXTENDED could crash for UNION queries in which the last SELECT was not parenthesized and included an ORDER BY clause. (Bug #43612)

  • SELECT ... INTO @var could produce values different from SELECT ... without the INTO clause. (Bug #42009)

  • Using --hexdump together with --read-from-remote-server caused mysqlbinlog to crash. (Bug #41943)

  • A crash occurred due to a race condition between the merge table and table_cache evictions.

    00000001403C452F    mysqld.exe!memcpy()[memcpy.asm:151]
    00000001402A275F    mysqld.exe!ha_myisammrg::info()[]
    00000001402A2471    mysqld.exe!ha_myisammrg::attach_children()[]
    00000001402A2788    mysqld.exe!ha_myisammrg::extra()[]
    000000014015FC5D    mysqld.exe!attach_merge_children()[]
    000000014016A4C1    mysqld.exe!open_tables()[]
    000000014016A898    mysqld.exe!open_and_lock_tables_derived()[]
    000000014018BB54    mysqld.exe!mysql_insert()[]
    000000014019EDD3    mysqld.exe!mysql_execute_command()[]
    00000001401A2F06    mysqld.exe!mysql_parse()[]
    00000001401A3C1A    mysqld.exe!dispatch_command()[]
    00000001401A4CD7    mysqld.exe!do_command()[]
    0000000140246327    mysqld.exe!handle_one_connection()[]
    00000001402B82C5    mysqld.exe!pthread_start()[my_winthread.c:85]
    00000001403CAC37    mysqld.exe!_callthreadstart()[thread.c:295]
    00000001403CAD05    mysqld.exe!_threadstart()[thread.c:275]
    0000000077D6B69A    kernel32.dll!BaseThreadStart()
    Trying to get some variables.
    Some pointers may be invalid and cause the dump to abort...

    (Bug #41212)

  • For some queries, an equality propagation problem could cause a = b and b = a to be handled differently. (Bug #40925)

  • For views created with a column list clause, column aliases were not substituted when selecting through the view using a HAVING clause. (Bug #40825)

  • A multiple-table DELETE involving a table self-join could cause a server crash. (Bug #39918)

  • Creating an InnoDB table with a comment containing a '#' character caused foreign key constraints to be omitted. (Bug #39793)

  • The mysql option --ignore-spaces was nonfunctional. (Bug #39101)

  • If a query was such as to produce the error 1054 Unknown column '...' in 'field list', using EXPLAIN EXTENDED with the query could cause a server crash. (Bug #37362)

Download these Release Notes
PDF (US Ltr) - 2.1Mb
PDF (A4) - 2.1Mb
EPUB - 0.6Mb