MySQLニュース

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

オリジナル版:http://dev.mysql.com/doc/refman/5.1/en/news-5-1-58.html

最も普及しているオープンソースデータベース管理システムの新バージョンMySQL Community Server 5.1.58がリリースされました。MySQL 5.1.58は、プロダクションシステムでの使用をお勧めします。

MySQL 5.1の新機能の概要については、以下を参照してください。

http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html

新たなサーバにMySQL 5.1.58をインストール、または以前のMySQLリリースからMySQL 5.1.58にアップグレードする際の情報については、以下を参照してください。

http://dev.mysql.com/doc/refman/5.1/en/installing.html

下記のダウンロードページから、MySQLサーバのソースコード及び多数のプラットフォーム用バイナリが入手可能です

http://dev.mysql.com/downloads/

現時点ですべてのミラーサイトが最新であるとは限らないことに注意してください。
あるミラーサイトで本バージョンを見つけることができない場合は、後日再確認を行うか、別のダウンロード・サイトを選択してください。

フィードバック、バグレポート、バグ修正、パッチ等の情報をお待ちしておりますので、以下のページをご利用ください。

http://forge.mysql.com/wiki/Contributing

MySQL 5.1に関するオープンな問題の情報については、以下のエラッタリストを参照してください。

http://dev.mysql.com/doc/refman/5.1/en/open-bugs.html

以下のセクションは、MySQL5.1の前リリース以降のMySQLソースコードの変更を記載しています。これはオンラインでも閲覧可能です:

http://dev.mysql.com/doc/refman/5.1/en/news-5-1-58.html

以下は、追加または変更された機能です。

Changes in MySQL 5.1.58 (July 5th, 2011)

Bugs fixed:

* InnoDB Storage Engine: If the server crashed while an XA
transaction was prepared but not yet committed, the
transaction could remain in the system after restart, and
cause a subsequent shutdown to hang. (Bug #11766513, Bug
#59641)

* Partitioning: When executing a row-ordered retrieval index
merge, the partitioning handler used memory from that
allocated for the table, rather than allocated to the
query, causing table object memory not to be freed until the
table was closed. (Bug #11766249, Bug #59316)

* Replication: When mysqlbinlog was invoked using
--base64-output=decode-row and --start-position=pos, (where
pos is a point in the binary log past the format description
log event), a spurious error of the type shown here was
generated:

malformed binlog: it does not contain any Format_description_log_event...

However, since there is nothing unsafe about not printing the
format description log event, the error has been removed for
this case. (Bug #12354268)

* Replication: Typographical errors appeared in the text of
several replication error messages. (The word "position" was
misspelled as "postion".) (Bug #11762616, Bug #55229)

* After the fix for Bug#11889186, MAKEDATE() arguments with a
year part greater than 9999 raised an assertion. (Bug
#12403504)

* An assertion could be raised due to a missing NULL value check
in Item_func_round::fix_length_and_dec(). (Bug #12392636)

* In debug builds on Solaris, an assertion was raised if a
reverse IP lookup with gethostbyaddr_r() failed. (Bug
#12377872)

* MySQL did not build if configured with both --with-debug and
--with-libedit. (Bug #12329909)

* A problem introduced in 5.1.57 caused very old (MySQL 4.0)
clients to be unable to connect to the server. (Bug #61222,
Bug #12563279)

* Using CREATE EVENT IF NOT EXISTS for an event that already
existed and was enabled caused multiple instances of the event
to run. (Bug #61005, Bug #12546938)

* The incorrect max_length value for YEAR values could be used
in temporary result tables for UNION, leading to incorrect
results. (Bug #59343, Bug #11766270)

* In Item_func_in::fix_length_and_dec(), a Valgrind warning for
uninitialized values was corrected. (Bug #59270, Bug
#11766212)

* In ROUND() calculations, a Valgrind warning for uninitialized
memory was corrected. (Bug #58937, Bug #11765923)

* Valgrind warnings caused by comparing index values to an
uninitialized field were corrected. (Bug #58705, Bug
#11765713)

* LOAD DATA INFILE errors could leak I/O cache memory. (Bug
#58072, Bug #11765141)

* For LOAD DATA INFILE, multibyte character sequences could be
pushed onto a stack too small to accommodate them. (Bug
#58069, Bug #11765139)

* An embedded client would abort rather than issue an error
message if it issued a TEE command (\T file_name) and the
directory containing the file did not exist. This occurred
because the wrong error handler was called. (Bug #57491, Bug
#11764633)

* In debug builds, Field_new_decimal::store_value() was subject
to buffer overflows. (Bug #55436, Bug #11762799)

* On Linux, the mysql client built using the bundled libedit did
not read ~/.editrc. (Bug #49967, Bug #11757855)

* The optimizer sometimes incorrectly processed HAVING clauses
for queries that did not also have an ORDER BY clause. (Bug
#48916, Bug #11756928)

* PROCEDURE ANALYZE() could leak memory for NULL results, and
could return incorrect results if used with a LIMIT clause.
(Bug #48137, Bug #11756242)

* On some platforms, the Incorrect value: xxx for column yyy at
row zzz error produced by LOAD DATA INFILE could have an
incorrect value of zzz. (Bug #46895, Bug #11755168)

* In MySQL 5.1 and up, if a table had triggers that used syntax
supported in 5.0 but not 5.1, the table became unavailable.
Now the table is marked as having broken triggers. (Bug
#45235, Bug #11753738)

* An attempt to install nonexistent files during installation
was corrected. (Bug #43247, Bug #11752142)

* On FreeBSD 64-built builds of the embedded server, exceptions
were not prevented from propagating into the embedded
application. (Bug #38965, Bug #11749418)

MySQLや関連ソリューションに関するお問い合わせ、お見積などがございましたら、ご連絡ください。

お問い合わせ各MySQL保守サービス見積依頼スマートスタイルOSSストア

ページトップへ