This is a Monthly Rapid Update release of the MySQL Enterprise Server 5.0.
This section documents all changes and bugfixes that have been applied since the last MySQL Enterprise Server release (5.0.74). 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.
Replication: When rotating relay log files, the slave deletes relay log files and then edits the relay log index file. Formerly, if the slave shut down unexpectedly between these two events, the relay log index file could then reference relay logs that no longer existed. Depending on the circumstances, this could when restarting the slave cause either a race condition or the failure of replication. (Bug #38826, Bug #39325)
In example option files provided in MySQL distributions, the
thread_stackvalue was increased from 64K to 128K. (Bug #41577)
INFORMATION_SCHEMA.SCHEMA_PRIVILEGEStable was limited to 7680 rows. (Bug #41079)
In debug builds, obsolete debug code could be used to crash the server. (Bug #41041)
Some queries that used a “range checked for each record” scan could return incorrect results. (Bug #40974)
References: See also Bug #44810.
SELECTqueries could fail with a
Duplicate entryerror. (Bug #40953)
IF(..., CAST(as an argument to an aggregate function could cause an assertion failure. (Bug #40761)
The server crashed if an integer field in a CSV file did not have delimiting quotation marks. (Bug #39616)
Creating a table with a comment of 62 characters or longer caused a server crash. (Bug #39591)
InnoDBcould hang trying to open an adaptive hash index. (Bug #39483)
Use of spatial data types in prepared statements could cause memory leaks or server crashes. (Bug #37956, Bug #37671)
DAYNAME()functions returned a binary string, so that using
UPPER()had no effect. Now
DAYNAME()return a value in
character_set_connectioncharacter set. (Bug #37575)
FULLTEXTsearches that used the truncation operator did not return matching records and calculated relevance incorrectly. (Bug #37245)
The code for the
InnoDBdid not handle errors from the
gettimeofday()system call. Now it retries
gettimeofday()several times and updates the value of the
Innodb_row_lock_time_maxstatus variable only if
ut_usectime()was successful. (Bug #36819)
A read past the end of the string could occur while parsing the value of the
--innodb-data-file-pathoption. (Bug #36149)
max_lengthmetadata value was calculated incorrectly for the
FORMAT()function, which could cause incorrect result set metadata to be sent to clients. (Bug #35558)
EXPLAIN EXTENDEDevaluation of aggregate functions that required a temporary table caused a server crash. (Bug #34773)
The mysql client incorrectly parsed statements containing the word “delimiter” in mid-statement.
This fix is different from the one applied for this bug in MySQL 5.0.66. (Bug #33812)
References: See also Bug #38158.
Queries executed using join buffering of
BITcolumns could produce incorrect results. (Bug #31399)
SSL support was not included in some “generic” RPM packages. (Bug #26760)