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


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




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

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

RPM Notes:

* The version information in RPM package files has been changed:
+ The "level" field of a MySQL version number is now also
included in the RPM version and in the package file name.
+ The RPM "release" value now starts to count from 0.
For example, the Rhel, Sles rpm file of 5.0.90 is named as

Bugs fixed:

* *Security Fix*: For servers built with yaSSL, a preauthorization
buffer overflow could cause memory corruption or a server
crash. We thank Evgeny Legerov from Intevydis for providing us
with a proof-of-concept script that allowed us to reproduce
this bug. (Bug#50227:

* *Replication*: FLUSH LOGS did not actually close and reopen the
binary log index file.
See also Bug#34582:

* Some prepared statements could raise an assertion when

* Valgrind warnings for CHECKSUM TABLE were corrected.

* Specifying an index algorithm (such as BTREE) for SPATIAL or
FULLTEXT indexes caused a server crash. These index types do
not support algorithm specification, and it is now disallowed
to do so. (Bug#49250:

* The optimizer sometimes incorrectly handled conditions of the
form WHERE col_name='const1' AND col_name='const2'.

* Several strmake() calls had an incorrect length argument (too
large by one).

* On Fedora 12, strmov() did not guarantee correct operation for
overlapping source and destination buffer. Calls were fixed to
use an overlap-safe version instead.

* Incomplete reset of internal TABLE structures could cause a
crash with eq_ref table access in subqueries.

* Re-execution of a prepared statement could cause a server
crash. (Bug#48508:

* The error message for ER_UPDATE_INFO was subject to buffer
overflow or truncation.

* On Solaris, no stack trace was printed to the error log after
a crash. (Bug#47391:

* Comparison with NULL values sometimes did not produce a
correct result.

* When compressed MyISAM files were opened, they were always
memory mapped, sometimes causing memory-swapping problems. To
deal with this, a new system variable, myisam_mmap_size, was
added to limit the amount of memory used for memory mapping of
MyISAM files.