Hery Ramilison MySQL Community Server 5.1.72 has been released
Sep 20, 2013; 09:33
Hery Ramilison
MySQL Community Server 5.1.72 has been released
Dear MySQL users,
MySQL Server 5.1.72, a new version of the popular Open Source Database Management System, has been released. MySQL 5.1.72 is recommended for use on production systems.
For an overview of what's new in MySQL 5.1, please see
MySQL Server is available in source and binary form for a number of platforms from our download pages at
http://dev.mysql.com/downloads/
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.
The following section lists the changes in the MySQL source code since the previous released version of MySQL 5.1. It may also be viewed online at
* InnoDB: The row_sel_sec_rec_is_for_clust_rec function would incorrectly prepare to compare a NULL column prefix in a secondary index with a non-NULL column in a clustered index. (Bug #17312846)
* InnoDB: An incorrect purge would occur when rolling back an update to a delete-marked record. (Bug #17302896)
* InnoDB: InnoDB would rename a user-defined foreign key constraint containing the string "_ibfk_" in its name, resulting in a duplicate constraint. (Bug #17076737, Bug #69693, Bug #17076718, Bug #69707)
* InnoDB: Rolling back an INSERT after a failed BLOB write would result in an assertion failure. The assertion has been modified to allow NULL BLOB pointers if an error occurs during a BLOB write. (Bug #16971045)
* InnoDB: The srv_master_thread background thread, which monitors server activity and performs activities such as page flushing when the server is inactive or in a shutdown state, runs on a one second delay loop. srv_master_thread would fail to check if the server is in a shutdown state before sleeping. (Bug #13417564, Bug #63276)
* InnoDB: An infinite loop could occur in buf_page_get_gen when handling compressed-only pages. (Bug #12560151, Bug #61132)
* Within a stored program, comparison of the value of a scalar subquery with an IN clause resulted in an error for the first execution and raised an assertion for the second execution. (Bug #17029399)
* The my_strtoll10() function could incorrectly convert some long string-format numbers to numeric values and fail to set the overflow flag. (Bug #16997513)
* For queries that accessed an INFORMATION_SCHEMA table in a subquery, and attempt to lock a mutex that had already been locked could cause a server crash. (Bug #11765744)
* For DIV expressions, assignment of the result to multiple variables could cause a server crash. (Bug #59241, Bug #11766191) References: See also Bug #8457.
* mysqldump wrote SET statements as SET OPTION, which failed when reloaded because the deprecated OPTION keyword has been removed from SET syntax. (Bug #67507, Bug #15844882)
* If one connection changed its default database and simultaneously another connection executed SHOW PROCESSLIST, the second connection could access invalid memory when attempting to display the first connection's default database. memory. (Bug #58198, Bug #11765252)
On behalf of Oracle MySQL RE Team
Hery Ramilison
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql
Search
Lasso Programming
This site manages and broadcasts several email lists pertaining to Lasso Programming and technologies related and used by Lasso developers. Sign up today!