MySQL Community Server 5.0.87がリリースされました


最も普及しているオープンソースデータベース管理システムの新バージョンであるMySQL Community Server 5.0.87がリリースされました。MySQL Community Server 5.0リリースシリーズにおける本リリースと以降のリリースは、MySQL Enterprise Serverのカウンターパートに対応するバージョン番号を共有します。




以下のセクションは、以前のリリースであるMySQL Community Server 5.0.86以来のMySQLソースコードにおけるバージョン間の変更を記載しています。

あなたが使用するバージョンおよび機能と関係のある修正に関するより詳細かつ個別の更新アラートを受けたい場合、MySQL Enterpriseへの申し込みを検討してください。(商用でMySQLが提供しています)。より詳細な個別の修正情報は以下を参照してください。


C.1.1. Changes in MySQL 5.0.87

This section documents all changes and bugfixes that have been
applied since the last MySQL Enterprise Server and MySQL Community
Server release (5.0.86). If you would like to receive more
fine-grained and personalized update alerts about fixes that are
relevant to the version and features you use, please consider
subscribing to MySQL Enterprise (a commercial MySQL offering). For
more details please see

Bugs fixed:

* Incompatible Change: In binary installations of MySQL, the
supplied binary-configure script would start and configure
MySQL, even when request help on the command with the --help
command-line option. The --help, if provided, will no longer
start and install the server.

* Replication: BEGIN statements were not included in the output
of mysqlbinlog. (Bug#46998:

* Replication: Database-level character sets were not always
honored by the replication SQL thread. This could cause data
inserted on the master using LOAD DATA to be replicated using
the wrong character set.

* API: The fix for Bug#24507: could
lead in some cases to client application failures due to a
race condition. Now the server waits for the "dummy" thread to
return before exiting, thus making sure that only one thread
can initialize the POSIX threads library.

* On Mac OS X or Windows, sending a SIGHUP signal to the server
or an asynchronous flush (triggered by flush_time) caused the
server to crash. (Bug#47525:

* Solaris binary packages now are compiled with -g0 rather than
-g. (Bug#47137:

* EXPLAIN caused a server crash for certain valid queries.

* When creating a new instance on Windows using mysqld-nt and
the --install parameter, the value of the service would be set
incorrectly, resulting in a failure to start the configured
service. (Bug#46917:

* The server crashed when re-using outer column references in
correlated subqueries when the enclosing query used a temp
table. (Bug#46791:

* The server ignored the setting of sync_frm for CREATE TABLE
... LIKE. (Bug#46591:

* An attempt to create a table with the same name as an existing
view could cause a server crash.

* A memory leak occurred when EXPLAIN encountered a malformed
query. (Bug#45989:

* When re-installing MySQL on Windows on a server that has a
data directory from a previous MySQL installation, the
installer would fail to identify the existence of the
installation and the password configured for the root user.

* Client flags were incorrectly initialized for the embedded
server, causing several tests in the jp test suite to fail.

* A test for stack growth failed on some platforms, leading to
server crashes. (Bug#42213:

* MySQL server used the wrong lock type (always TL_READ instead
of TL_READ_NO_INSERT when appropriate) for tables used in
subqueries of UPDATE statements. This led in some cases to
replication failure because statements were written in the
wrong order to the binary log.

* myisamchk performed parameter value casting at startup that
generated unnecessary warning messages.

* When building MySQL on Windows from source, the
WITH_BERKELEY_STORAGE_ENGINE option would fail to configure
BDB support correctly.

* 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.