diff options
| author | adam <adam@pkgsrc.org> | 2013-10-01 11:00:39 +0000 |
|---|---|---|
| committer | adam <adam@pkgsrc.org> | 2013-10-01 11:00:39 +0000 |
| commit | 31f39ad23e27841a14eed8d1ef20f97f18a5455a (patch) | |
| tree | 93182f4b2074d09318f5aa4f8a78543d853cb79d /databases/mysql51-server/distinfo | |
| parent | 170f293e4ac5bf286fcbc5f62903f582eb5781c5 (diff) | |
| download | pkgsrc-31f39ad23e27841a14eed8d1ef20f97f18a5455a.tar.gz | |
Changes 5.1.72:
* 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.
* InnoDB: An incorrect purge would occur when rolling back an update to a delete-marked record.
* InnoDB: InnoDB would rename a user-defined foreign key constraint containing the string “_ibfk_” in its name, resulting in a duplicate constraint.
* 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.
* 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.
* InnoDB: An infinite loop could occur in buf_page_get_gen when handling compressed-only pages.
* 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.
* The my_strtoll10() function could incorrectly convert some long string-format numbers to numeric values and fail to set the overflow flag.
* 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.
* For DIV expressions, assignment of the result to multiple variables could cause a server crash.
* mysqldump wrote SET statements as SET OPTION, which failed when reloaded because the deprecated OPTION keyword has been removed from SET syntax.
* 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.
Diffstat (limited to 'databases/mysql51-server/distinfo')
| -rw-r--r-- | databases/mysql51-server/distinfo | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/databases/mysql51-server/distinfo b/databases/mysql51-server/distinfo index 078ee0eb186..d3acedc4e07 100644 --- a/databases/mysql51-server/distinfo +++ b/databases/mysql51-server/distinfo @@ -1,8 +1,8 @@ -$NetBSD: distinfo,v 1.29 2013/08/22 11:09:46 christos Exp $ +$NetBSD: distinfo,v 1.30 2013/10/01 11:00:39 adam Exp $ -SHA1 (mysql-5.1.71.tar.gz) = a71c77c43aa8374ccb6e09f0ad7f225846af59e6 -RMD160 (mysql-5.1.71.tar.gz) = 4077b4aab7297a48b5dc180acf35c9a94bce366c -Size (mysql-5.1.71.tar.gz) = 24033179 bytes +SHA1 (mysql-5.1.72.tar.gz) = af1f46e56402b38a085ac592cd7df3aa25e9cea2 +RMD160 (mysql-5.1.72.tar.gz) = a5ba8bedf4027af90a4612a1a7f3a848999cfbf5 +Size (mysql-5.1.72.tar.gz) = 24044338 bytes SHA1 (patch-aa) = 2a5321738e637a56e57cd6b1b40908d2bf275506 SHA1 (patch-ab) = 4c485a74d55553d63fc3dbc0350d0aa0068e1fcf SHA1 (patch-ac) = bfb6eec77d7c5aa8d2b849632769005dcf2e272c |