2012年5月15日

[installer 3216] mysql-5.1.63, 5.5.24

mysql-5.1.63, 5.5.24 出ています。

詳細不明ですが、Security Fix が入っています。

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

D.1.1 Changes in MySQL 5.1.63 (07 May 2012)
------------------------------------------------

*Bugs Fixed*

* *Security Fix*: Bug #64884 was fixed.

* *Security Fix*: Bug #59387 was fixed.

* *InnoDB Storage Engine*: Deleting a huge amount of data from
`InnoDB' tables within a short time could cause the purge
operation that flushes data from the buffer pool to stall. If this
issue occurs, restart the server to work around it. This issue is
only likely to occur on 32-bit platforms. (Bug #13847885)

* *InnoDB Storage Engine*: If the server crashed during a *Note
`TRUNCATE TABLE': truncate-table. or *Note `CREATE INDEX':
create-index. statement for an `InnoDB' table, or a *Note `DROP
DATABASE': drop-database. statement for a database containing
`InnoDB' tables, an index could be corrupted, causing an error
message when accessing the table after restart:

InnoDB: Error: trying to load index INDEX_NAME for table TABLE_NAME
InnoDB: but the index tree has been freed!

In MySQL 5.1, this fix applies to the InnoDB Plugin, but not the
built-in InnoDB storage engine. (Bug #12861864, Bug #11766019)

* *InnoDB Storage Engine*: When data was removed from an `InnoDB'
table, newly inserted data might not reuse the freed disk blocks,
leading to an unexpected size increase for the system tablespace
or `.ibd' file (depending on the setting of
`innodb_file_per_table'. The *Note `OPTIMIZE TABLE':
optimize-table. could compact a `.ibd' file in some cases but not
others. The freed disk blocks would eventually be reused as
additional data was inserted. (Bug #11766634, Bug #59783)

* *Partitioning*: After updating a row of a partitioned table and
selecting that row within the same transaction with the query
cache enabled, then performing a *Note `ROLLBACK': commit, the
same result was returned by an identical *Note `SELECT': select.
issued in a new transaction. (Bug #11761296, Bug #53775)

* *Replication*: The `--relay-log-space-limit' option was sometimes
ignored.

More specifically, when the SQL thread went to sleep, it allowed
the I/O thread to queue additional events in such a way that the
relay log space limit was bypassed, and the number of events in
the queue could grow well past the point where the relay logs
needed to be rotated. Now in such cases, the SQL thread checks to
see whether the I/O thread should rotate and provide the SQL
thread a chance to purge the logs (thus freeing space).

Note that, when the SQL thread is in the middle of a transaction,
it cannot purge the logs; it can only ask for more events until
the transaction is complete. Once the transaction is finished, the
SQL thread can immediately instruct the I/O thread to rotate.
(Bug #12400313, Bug #64503) References: See also Bug #13806492.

* Mishandling of `NO_BACKSLASH_ESCAPES' SQL mode within stored
procedures on slave servers could cause replication failures.
(Bug #12601974)

* If the system time was adjusted backward during query execution,
the apparent execution time could be negative. But in some cases
these queries would be written to the slow query log, with the
negative execution time written as a large unsigned number. Now
statements with apparent negative execution time are not written
to the slow query log. (Bug #63524, Bug #13454045) References:
See also Bug #27208.

* *Note `SHOW': show. statements treated stored procedure, stored
function, and event names as case sensitive. (Bug #56224, Bug
#11763507)

* On Windows, *Note `mysqlslap': mysqlslap. crashed for attempts to
connect using shared memory. (Bug #31173, Bug #11747181, Bug
#59107, Bug #11766072)


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

D.1.1 Changes in MySQL 5.5.24 (07 May 2012)
------------------------------------------------

*Functionality Added or Changed*

* *Important Change*: *Replication*: INSERT ON DUPLICATE KEY UPDATE
is now marked as unsafe for statement-based replication if the
target table has more than one primary or unique key. For more
information, see Section 16.1.2.3, "Determination of Safe and
Unsafe Statements in Binary Logging".

*Bugs Fixed*

* *Security Fix*: Bug #64884 was fixed.

* If the `--bind-address' option was given a host name value and the
host name resolved to more than one IP address, the server failed
to start. For example, with `--bind-address=localhost', if
`localhost' resolved to both `127.0.0.1' and `::1', startup
failed. Now the server prefers the IPv4 address in such cases.
(Bug #61713, Bug #12762885)

* On Windows, *Note `mysqlslap': mysqlslap. crashed for attempts to
connect using shared memory. (Bug #31173, Bug #11747181, Bug
#59107, Bug #11766072)

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


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




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