pkgsrc/databases/mysql51-client/distinfo
adam 753c5efb75 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.
2013-10-01 11:00:39 +00:00

30 lines
1.7 KiB
Text

$NetBSD: distinfo,v 1.26 2013/10/01 11:00:39 adam Exp $
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) = 344bc9ab7013fbf64be6adbe8a9fc6279887beb1
SHA1 (patch-ab) = a1c699ebd9dc7e2cec9354035cbd9fdc2a411175
SHA1 (patch-ac) = a250b9797fbaad51d054cbb324feb0f7c29096d4
SHA1 (patch-ad) = 4e98f696b8b5098456e53a8de710a6bcd547997c
SHA1 (patch-ae) = 1bcec45f4cd221ba6e1d176caf01dbd3b3dbfa88
SHA1 (patch-af) = 6f310d2e033999bf2637659223bdd787f3954884
SHA1 (patch-ag) = 20e4f5ac5e7b7927339b8c46329533f29a3df56f
SHA1 (patch-ah) = 715bef16c95e26f4abb39eb05fd23dbc9f7fa96b
SHA1 (patch-ai) = 625474e24c6f6c7b921ffd1534fd2ff93fdf02c8
SHA1 (patch-aj) = 5b67806269894c6f1725716f96433643260184db
SHA1 (patch-ak) = af5309d7a5b48042368936c7540f90df3dc4aafe
SHA1 (patch-am) = 162c97a87ab00b407f6796b55ef839ba2e3ac2af
SHA1 (patch-an) = a608060cee7aadaf8bcde84016a73131a75dea32
SHA1 (patch-ao) = dbf68af2d2ded85140aac3602d4f6ce5d68cc78a
SHA1 (patch-ap) = 8d27b99a54071dce99f3b287676ed88c93028cc0
SHA1 (patch-aq) = d04016a2ab84709aee0c08aef71c2f79e82fc6f3
SHA1 (patch-ar) = bc0e2083ec285be8adac1027e63bf076e4c57211
SHA1 (patch-as) = 5eb3a9308b13a25fa813db0ed4a06f8e43db74f6
SHA1 (patch-at) = b51e9044727447065cef267a469c481b66ccf64c
SHA1 (patch-au) = e454e1a4f4232e57f2105ac5150e1df0be709864
SHA1 (patch-av) = b8fb1065d7e71522374a16d759d2f3ab5227f590
SHA1 (patch-aw) = 50b811871b68506131020750f9af41e6834ec1cb
SHA1 (patch-ax) = 390debbc31e710f5aa41fda6a8b1134a14a2ff23
SHA1 (patch-ay) = 0b9c334c1e50c0c341e38d3fb189194de2d05b87
SHA1 (patch-vio_viossl.c) = ad922587684a635a82c2fa662be7431c63063909