MySQL 5.1.19ベータ版がリリースされました。


最も普及しているオープンソースデータベースの新ベータバージョンであるMySQL 5.1.19ベータ版がリリースされました。

これはベータ版であり、他の多くの試作商品リリースと同様、商品レベルのシステムまたは、重要なデータを含むシステムに対してインストールしないように注意してください。5.0使用の商品レベルのシステムについては、以下のMySQL Enterpriseの商品説明のページをご覧ください。


MySQL 5.1.19ベータ版は、http://dev.mysql.com/downloads/とミラーサイトのダウンロード・ページから、ソースコード及び多くのプラットフォームのためのバイナリで現在利用可能です。







   * Bug#28783 may occur during high load (http://bugs.mysql.com/28783)
     The bug will manifest itself by a ndbd node missing heartbeats and
     consequently shutting down.
     The release should function well under "normal" operation and may be
     used for evaluation purposes, however is not suited for high load
     testing, as it is likely to hit this bug.
     If you wish to evaluate cluster in a high load situation, please use
     5.1.18 or wait for 5.1.20.


Functionality added or changed:
   * INSERT DELAYED statements for BLACKHOLE tables caused a server
     crash. The BLACKHOLE storage engine now supports INSERT
     DELAYED. (Bug#27998:http://bugs.mysql.com/27998)
   * The BLACKHOLE storage engine now supports LOCK TABLES and
     UNLOCK TABLES. (Bug#26241:http://bugs.mysql.com/26241)
   * The data type used for the VARIABLE_VALUE column of the
     following INFORMATION_SCHEMA tables has been changed to
     For more information, see Section 22.24, "The
     SESSION_VARIABLES Tables," and

Bugs fixed:
   * Security fix: Use of a view could allow a user to gain update
     privileges for tables in other databases.
   * Security fix: UDFs are supposed to be loadable only from the
     plugin directory, but this restriction was not being enforced.
   * NDB Cluster: When an API node sent more than 1024 signals in a
     single batch, NDB would process only the first 1024 of these,
     and then hang. (Bug#28443:http://bugs.mysql.com/28443)
   * NDB Cluster (Disk Data): DDL operations were not supported on
     a partially started cluster.
   * NDB Cluster: A delay in obtaining AUTO_INCREMENT IDs could
     lead to excess temporary errors.
   * NDB Cluster: Local checkpoint files related to dropped NDB
     tables were not removed.
   * NDB Cluster: A failure to release internal resources following
     an error could lead to problems with single user mode.
   * NDB Cluster: Multiple operations involving deletes followed by
     reads were not handled correctly.
     Note: This issue could also affect MySQL Cluster Replication.
   * NDB Cluster (Disk Data): Extremely large inserts into Disk
     Data tables could lead to data node failure in some
     circumstances. (Bug#27942:http://bugs.mysql.com/27942)
   * NDB Cluster: Repeated insertion of data generated by mysqldump
     into NDB tables could eventually lead to failure of the
     cluster. (Bug#27437:http://bugs.mysql.com/27437)
   * NDB Cluster: Restarting a data node caused SQL nodes to log
     repeatedly and unnecessarily the status of the event buffer.
     (This issue was known to occur in MySQL 5.1.16 and later
   * NDB Cluster: ndb_mgmd failed silently when the cluster
     configuration file contained invalid [TCP] entries.
   * NDB Cluster: ndb_connectstring did not appear in the output of
     SHOW VARIABLES. (Bug#26675:http://bugs.mysql.com/26675)
   * NDB Cluster (APIs): In a multi-operation transaction, a delete
     operation followed by the insertion of an implicit NULL failed
     to overwrite an existing value.
   * Changing the size of a key buffer that is under heavy use
     could cause a server crash. The fix partially removes the
     limitation that LOAD INDEX INTO CACHE fails unless all indexes
     in a table have the same block size. Now the statement fails
     only if IGNORE LEAVES is specified.
   * EXPLAIN for a query on an empty table immediately after its
     creation could result in a server crash.
   * Grouping queries with correlated subqueries in WHERE
     conditions could produce incorrect results.
   * libmysql.dll could not be dynamically loaded on Windows.
   * Portability problems caused by use of isinf() were corrected.
   * Using a TEXT local variable in a stored routine in an
     expression such as SET var = SUBSTRING(var, 3) produced an
     incorrect result. (Bug#27415:http://bugs.mysql.com/27415)
   * A large filesort could result in a division by zero error and
     a server crash. (Bug#27119:http://bugs.mysql.com/27119)
   * The server could abort or deadlock for INSERT DELAYED
     statements for which another insert was performed implicitly
     (for example, via a stored function that inserted a row).
   * The server could hang for INSERT IGNORE ... ON DUPLICATE KEY
     UPDATE if an update failed.
   * Quoted labels in stored routines were mishandled, rendering
     the routines unusable.
   * Changes to some system variables should invalidate statements
     in the query cache, but invalidation did not happen.
   * Some ALTER TABLE statements that worked in MySQL 5.0 did not
     work in 5.1. (Bug#28415:http://bugs.mysql.com/28415)
   * Flow control optimization in stored routines could cause
     exception handlers to never return or execute incorrect logic.
   * An attempt to execute CREATE TABLE ... SELECT when a temporary
     table with the same name already existed led to the insertion
     of data into the temporary table and creation of an empty
     non-temporary table. (Bug#24508:http://bugs.mysql.com/24508)
   * Concurrent execution of CREATE TABLE ... SELECT and other
     statements involving the target table suffered from various
     race conditions, some of which might have led to deadlocks.
   * CREATE TABLE IF NOT EXISTS ... SELECT caused a server crash if
     the target table already existed and had a BEFORE INSERT
     trigger. (Bug#20903:http://bugs.mysql.com/20903)
   * Deadlock occurred for attempts to execute CREATE TABLE IF NOT
     EXISTS ... SELECT when LOCK TABLES had been used to acquire a
     read lock on the target table.
   * It was not possible to use the value -9223372036854775808
     (that is, -MAXVALUE + 1) when specifying a LIST partition.
   * Some InnoDB variables were missing from the output of mysqld
     --verbose --help. (Bug#26987:http://bugs.mysql.com/26987)
   * CAST() to DECIMAL did not check for overflow.
   * Views ignored precision for CAST() operations.
   * For InnoDB, in some rare cases the optimizer preferred a more
     expensive ref access to a less expensive range access.
   * A query with a NOT IN subquery predicate could cause a crash
     when the left operand of the predicate evaluated to NULL.
   * Comparisons of DATE or DATETIME values for the IN() function
     could yield incorrect results.
   * LOAD DATA did not use CURRENT_TIMESTAMP as the default value
     for a TIMESTAMP column for which no value was provided.