2012年6月 1日

[installer 3238] mysql-5.5.25

mysql-5.5.25 出ています。

☆ mysql-5.5.25
http://www.mysql.com/
http://dev.mysql.com/downloads/mysql/5.5.html

D.1.2. Changes in MySQL 5.5.25 (Not yet released)
------------------------------------------------


*Functionality Added or Changed*

* The --safe-mode server option now is deprecated and will be
removed in MySQL 5.6.

*Bugs Fixed*

* *Performance*: *InnoDB*: Improved the algorithm related to
adaptive flushing. This fix increases the rate of flushing in
cases where compression is used and the data set is larger than
the buffer pool, leading to eviction. (Bug #13990648, Bug #65061)

* *InnoDB*: In a transaction using the REPEATABLE READ isolation
level, an UPDATE or DELETE statement for an InnoDB table could
sometimes overlook rows recently committed by other transactions.
As explained in Section 14.3.9.2, "Consistent Nonlocking Reads",
DML statements within a REPEATABLE READ transaction apply to rows
committed by other transactions, even if a query could not see
those rows. (Bug #14007649, Bug #65111)

* *InnoDB*: The Innodb_buffer_pool_pages_flushed status variable
was incorrectly set to twice the value it should be. Its value
should never exceed the value of Innodb_pages_written. (Bug
#14000361, Bug #65030)

* *InnoDB*: The error handling and message was improved for
attempting to create a foreign key with a column referencing
itself. The message suggested a potential problem with the data
dictionary, when no such problem existed. (Bug #12902967)

* *InnoDB*: The CHECK TABLE statement could fail for a large InnoDB
table due to a timeout value of 2 hours. For typical storage
devices, the issue could occur for tables that exceeded
approximately 200 or 350 GB, depending on I/O speed. The fix
relaxes the locking performed on the table being checked, which
makes the timeout less likely. It also makes InnoDB recognize
the syntax CHECK TABLE QUICK, which avoids the possibility of
the timeout entirely. (Bug #11758510, Bug #50723)

* *Replication*: It was theoretically possible for concurrent
execution of more than one instance of SHOW BINLOG EVENTS to
crash the MySQL Server. (Bug #13979418)

* *Replication*: Statements using AUTO_INCREMENT, LAST_INSERT_ID(),
RAND(), or user variables could be applied in the wrong context
on the slave when using statement-based replication and
replication filtering server options (see Section 16.2.3, "How
Servers Evaluate Replication Filtering Rules"). (Bug #11761686,
Bug #54201)

* *References*: See also Bug #11754117, Bug #45670, Bug #11746146,
Bug #23894.

* *Replication*: An INSERT into a table that has a composite
primary key that includes an AUTO_INCREMENT column that is not
the first column of this composite key is not safe for
statement-based binary logging or replication. Such statements
are now marked as unsafe and fail with an error when using the
STATEMENT binary logging format. For more information, see
Section 16.1.2.3, "Determination of Safe and Unsafe Statements
in Binary Logging", as well as Section 16.4.1.1, "Replication
and AUTO_INCREMENT".

Note
Tables using the InnoDB storage engine are not affected by this
issue, since InnoDB does not allow the creation of a composite
key that includes an AUTO_INCREMENT column, where this column
is not the first column in the key.

(Bug #11754117, Bug #45670)

* *References*: See also Bug #11761686, Bug #54201, Bug #11746146,
Bug #23894.

* SHOW TABLES was very slow unless the required information was
already in the disk cache. (Bug #60961, Bug #12427262)

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


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




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