kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/databases/mysql51-server/distinfo

33 lines
1.9 KiB
Text
Raw Normal View History

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 13:00:39 +02:00
$NetBSD: distinfo,v 1.30 2013/10/01 11:00:39 adam Exp $
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
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 13:00:39 +02:00
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
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
SHA1 (patch-aa) = 2a5321738e637a56e57cd6b1b40908d2bf275506
Fix building with Clang.
2011-03-17 14:26:04 +01:00
SHA1 (patch-ab) = 4c485a74d55553d63fc3dbc0350d0aa0068e1fcf
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
SHA1 (patch-ac) = bfb6eec77d7c5aa8d2b849632769005dcf2e272c
SHA1 (patch-ad) = 5fd4db0e04a97289f38a5467bbae5041f4082b51
don't use gethostbyname_r unless there is a prototype in scope.
2013-08-22 13:09:46 +02:00
SHA1 (patch-ae) = 3b9a0822b2fab21dea57b12d005eeae0ef9f66be
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
SHA1 (patch-af) = 1e13ba542b4fc2a1d59fc822d06c76bc4e92dc23
Update mysql51-{client,server} package to 5.1.51, MySQL 5.1.51. For full changes, please refer: http://dev.mysql.com/doc/refman/5.1/en/news-5-1-51.html Here is summary for security fixes: * Security Fix: During evaluation of arguments to extreme-value functions (such as LEAST() and GREATEST()), type errors did not propagate properly, causing the server to crash. (Bug#55826) * Security Fix: The server could crash after materializing a derived table that required a temporary table for grouping. (Bug#55568) * Security Fix: A user-variable assignment expression that is evaluated in a logical expression context can be precalculated in a temporary table for GROUP BY. However, when the expression value is used after creation of the temporary table, it was re-evaluated, not read from the table and a server crash resulted. (Bug#55564) * Security Fix: Pre-evaluation of LIKE predicates during view preparation could cause a server crash. (Bug#54568) * Security Fix: GROUP_CONCAT() and WITH ROLLUP together could cause a server crash. (Bug#54476) * Security Fix: Queries could cause a server crash if the GREATEST() or LEAST() function had a mixed list of numeric and LONGBLOB arguments, and the result of such a function was processed using an intermediate temporary table. (Bug#54461) * Security Fix: Queries with nested joins could cause an infinite loop in the server when used from stored procedures and prepared statements. (Bug#53544) * Security Fix: The PolyFromWKB() function could crash the server when improper WKB data was passed to the function. (Bug#51875)
2010-10-06 14:37:58 +02:00
SHA1 (patch-ag) = 85df1a0080376c5aff1a963e5532cb2c1ec5949d
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
SHA1 (patch-ah) = a608060cee7aadaf8bcde84016a73131a75dea32
SHA1 (patch-ai) = 4c5acf2b0e05765a1fe9e30558d163886e1aa492
Update mysql51-client and mysql51-server to 5.1.49. Please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-49.html for full changes. * InnoDB Plugin has been upgraded to version 1.0.10. This version is considered of General Availability (GA) quality. In this release, the InnoDB Plugin is included in source and binary distributions, except RHEL3, RHEL4, SuSE 9 (x86, x86_64, ia64), and generic Linux RPM packages. It also does not work for FreeBSD 6 and HP-UX or for Linux on generic ia64. Bugs fixed: * Security Fix: After changing the values of the innodb_file_format or innodb_file_per_table configuration parameters, DDL statements could cause a server crash. (Bug#55039) * Security Fix: Joins involving a table with with a unique SET column could cause a server crash. (Bug#54575) * Security Fix: Incorrect handling of NULL arguments could lead to a crash for IN() or CASE operations when NULL arguments were either passed explicitly as arguments (for IN()) or implicitly generated by the WITH ROLLUP modifier (for IN() and CASE). (Bug#54477) * Security Fix: A malformed argument to the BINLOG statement could result in Valgrind warnings or a server crash. (Bug#54393) * Security Fix: Use of TEMPORARY InnoDB tables with nullable columns could cause a server crash. (Bug#54044) * Security Fix: The server could crash if there were alternate reads from two indexes on a table using the HANDLER interface. (Bug#54007) * Security Fix: Using EXPLAIN with queries of the form SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...) could cause a server crash. (Bug#52711) * Security Fix: LOAD DATA INFILE did not check for SQL errors and sent an OK packet even when errors were already reported. Also, an assert related to client-server protocol checking in debug servers sometimes was raised when it should not have been. (Bug#52512)
2010-08-12 01:18:04 +02:00
SHA1 (patch-aj) = b8f35d3a1bc45eb5336ae6a842898b257d2660db
SHA1 (patch-ak) = 3c740b78afacfe05aa082c5b235c10c51ac94641
Fix broken patch. The files to patch must not include the name of the work directory.
2011-03-19 16:40:15 +01:00
SHA1 (patch-al) = ca9406a8b01dffb3f515f132fa7aaef66c78f2be
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
SHA1 (patch-am) = 2cf10915f5dc3caf11bb8c7c7255842da646b247
SHA1 (patch-an) = 7b627ceb6212641b7e0de9fd7142bc95e4dcb8cb
SHA1 (patch-ao) = 7895abad117d5c6901c2241209c5747e6c490e7d
SHA1 (patch-ap) = f356d4d26acdf0532fe70a49d0292878f600ff51
SHA1 (patch-aq) = 8e6029d36b290b9ffd964c38afe4352a9107be40
SHA1 (patch-ar) = ed9c062adce41a840db1e908ab0657db6de540ae
SHA1 (patch-as) = 8167416a083a011ded19d176bc488c94d9eb7abf
Add mysqlmanager, ndb-cluster and pstack PKG_OPTIONS. These are control some optional functions for mysql51-server (leaf package). Bump PKGREVISION.
2010-03-21 15:41:41 +01:00
SHA1 (patch-at) = 307a0785190f8bc175226ce83288cc85f7da4631
SHA1 (patch-au) = 51291771b994d199fb6de6a17dd7809a7bf39b68
Importing mysql51-server 5.1.44, server part of MySQL 5.1.44 including embedded server (by PKG_OPTION). For release MySQL 5.1 specific information please refer: http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html MySQL is a SQL (Structured Query Language) database server. SQL is the most popular database language in the world. MySQL is a client-server implementation that consists of a server daemon `mysqld' and many different client programs/libraries. The main goals of MySQL are speed and robustness. The base upon which MySQL is built is a set of routines that have been used in a highly demanding production environment for many years. While MySQL is still in development it already offers a rich and highly useful function set. The official way to pronounce 'MySQL' is 'My Ess Que Ell' (Not MY-SEQUEL). This package contains the MySQL server programs and libraries including embedded server (by PKG_OPTION).
2010-03-04 17:28:57 +01:00
SHA1 (patch-ax) = dbf68af2d2ded85140aac3602d4f6ce5d68cc78a
don't use gethostbyname_r unless there is a prototype in scope.
2013-08-22 13:09:46 +02:00
SHA1 (patch-include_my__net.h) = 5cfe4c14ea39ce806c615a87a13c74b48d159ffa
SHA1 (patch-mysys_my__net.c) = 1ee22921d62ccefc41bc9a81b96a576ce391f054
SHA1 (patch-mysys_my__thr__init.c) = ee03f554b38b1477ab13912333e09cab340b5f56
Fix build on a mix of GNU/Sun tools.
2012-03-09 13:38:27 +01:00
SHA1 (patch-sql_ha_ndbcluster.cc) = eb076bbce9d1d671331b41f50cf0be220cca7c6b
Changes 5.1.71: Functionality Added or Changed * comp_err now checks to make sure that new errors are not being added to MySQL 5.1 or 5.5 because the set of errors for these series is frozen. Bugs Fixed * InnoDB: During an insert buffer merge, InnoDB would invoke lock_rec_restore_from_page_infimum() on a potentially invalid record pointer. * InnoDB: The page_zip_validate() consistency check would fail after compressing a page, in page_zip_compress(). This problem was caused by page_zip_decompress(), which would fail to set heap_no correctly when a record contained no user data bytes. A record with no user data bytes occurs when, for example, a primary key is an empty string and all secondary index fields are NULL or an empty string. * InnoDB: The pthread_mutex, commit_threads_m, which was initialized but never used, has been removed from the code base. * Partitioning: When dropping a partitioned table, the table's .par file was deleted first, before the table definition or data. This meant that, if the server failed during the drop operation, the table could be left in an inconsistent state in which it could neither be accessed nor dropped. * Shared-compatibility conflict errors occurred for RPM install operations, even if no shared-compatibility RPMs were already installed. * A user variable referenced during execution of a prepared statement is set to memory that is freed at the end of execution. A second execution of the statement could result in Valgrind warnings when accessing this memory. * Misoptimization of left expressions in prepared statements could cause a server exit. * Subsequent to Prepared statement needs to be re-prepared errors, inserts into DECIMAL columns caused a server exit. * Assigning the result of a subquery to a user variable raised an assertion when the outer query included DISTINCT and GROUP BY.
2013-08-04 12:20:24 +02:00
SHA1 (patch-vio_viossl.c) = ad922587684a635a82c2fa662be7431c63063909
Reference in a new issue Copy permalink