2010年5月24日

[installer 2374] mysql-5.1.47

mysql-5.1.47 出ています。

複数のセキュリティホールの修正が含まれています。
http://dev.mysql.com/doc/refman/5.1/en/news-5-1-47.html
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-1848)
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-1849)
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-1850)
http://secunia.com/advisories/39792/

参照のこと。

☆ mysql-5.1.47
http://www.mysql.com/
http://dev.mysql.com/downloads/mysql/5.1.html

(付属の info ファイルは、
http://dev.mysql.com/doc/refman/5.1/en/news-5-1-47.html
と比べると大幅に情報が不足していますね…)

C.1.1 Changes in MySQL 5.1.47 (Not yet released)
------------------------------------------------

Bugs fixed:

* *Important Change*: *Replication*: When invoked, *Note `CHANGE
MASTER TO': change-master-to. and `SET GLOBAL
sql_slave_skip_counter' now cause information to be written to the
error log about the slave's state prior to execution of the
statement. For *Note `CHANGE MASTER TO': change-master-to, this
information includes the previous values for `MASTER_HOST',
`MASTER_PORT', `MASTER_LOG_FILE', and `MASTER_LOG_POS'. For *Note
`SET GLOBAL SQL_SLAVE_SKIP_COUNTER':
set-global-sql-slave-skip-counter, this information includes the
previous values of `sql_slave_skip_counter', the group relay log
name, and the group relay log position. (Bug#43406
http://bugs.mysql.com/bug.php?id=43406), Bug#43407
http://bugs.mysql.com/bug.php?id=43407))

* *Replication*: The failure of a *Note `REVOKE': revoke. statement
was logged with the wrong error code, causing replication slaves
to stop even when the failure was expected on the master.
(Bug#51987 http://bugs.mysql.com/bug.php?id=51987))

* Storage engine plugins on Windows could've been built with a
definition of `time_t' which was different from the server
expectations. The difference could cause affected plugins to
crash. In addition, the use of the `time_t' type in the storage
engine API layer has been enforced. (Bug#39802
http://bugs.mysql.com/bug.php?id=39802), Bug#40092
http://bugs.mysql.com/bug.php?id=40092))

* When using `UNINSTALL PLUGIN' to remove a loaded plugin, open
tables and connections caused *Note `mysqld': mysqld. to hang
until the open connections had been closed. (Bug#39053
http://bugs.mysql.com/bug.php?id=39053))

* 1) In rare cases, if a thread was interrupted during a *Note
`FLUSH PRIVILEGES': flush. operation, a debug assertion occurred
later due to improper diagnostic area setup. 2) A *Note `KILL':
kill. operation could cause a console error message referring to a
diagnostic area state without first ensuring that the state
existed. (Bug#33982 http://bugs.mysql.com/bug.php?id=33982))

----
こがよういちろう


投稿者 xml-rpc : 2010年5月24日 10:02
役に立ちました?:
過去のフィードバック 平均:(0) 総合:(0) 投票回数:(0)
本記事へのTrackback: http://hoop.euqset.org/blog/mt-tb2006.cgi/95919
トラックバック
コメント
コメントする




画像の中に見える文字を入力してください。