2011年3月 8日

[installer 2716] mysql-5.1.56

mysql-5.1.56 出ています。

☆ mysql-5.1.56
http://www.mysql.com/
http://downloads.mysql.com/archives.php?p=mysql-5.1&v=5.1.56
http://downloads.mysql.com/archives/mysql-5.1/mysql-5.1.56.tar.gz

http://dev.mysql.com/doc/refman/5.1/en/news-5-1.56.html がない…)


D.1.1 Changes in MySQL 5.1.56 (Not yet released)
------------------------------------------------

Functionality added or changed:

* *Note `mysqldump --xml': mysqldump. now displays comments from
column definitions. (Bug#13618
http://bugs.mysql.com/bug.php?id=13618))

Bugs fixed:

* *InnoDB Storage Engine*: *Note `InnoDB': innodb-storage-engine.
could could return values for `rows examined' in the query plan
that were higher than expected. `NULL' values were treated in an
inconsistent way. The inaccurate statistics could trigger `false
positives' in combination with the `MAX_JOIN_SIZE' setting,
because the queries did not really examine as many rows as
reported. (Bug#30423 http://bugs.mysql.com/bug.php?id=30423))

* *Partitioning*: Trying to use the same column more than once in
the partitioning key when partitioning a table by `KEY' caused
*Note `mysqld': mysqld. to crash. Such duplication of key columns
is now expressly disallowed, and fails with an appropriate error.
(Bug#53354 http://bugs.mysql.com/bug.php?id=53354), Bug#57924
http://bugs.mysql.com/bug.php?id=57924))

* *Replication*: When using the statement-based logging format,
*Note `INSERT ON DUPLICATE KEY UPDATE': insert-on-duplicate. and
*Note `INSERT IGNORE': insert. statements affecting transactional
tables that did not fail were not written to the binary log if
they did not insert any rows. (With statement-based logging, all
successful statements should be logged, whether they do or do not
cause any rows to be changed.) (Bug#59338
http://bugs.mysql.com/bug.php?id=59338))

* *Replication*: Formerly, *Note `STOP SLAVE': stop-slave. stopped
the slave I/O thread first and then stopped the slave SQL thread;
thus, it was possible for the I/O thread to stop after replicating
only part of a transaction which the SQL thread was executing, in
wich case--if the transaction could not be rolled back safely--the
SQL thread could hang.

Now, *Note `STOP SLAVE': stop-slave. stops the slave SQL thread
first and then stops the I/O thread; this guarantees that the I/O
thread can fetch any remaining events in the transaction that the
SQL thread is executing, so that the SQL thread can finish the
transaction if it cannot be rolled back safely. (Bug#58546
http://bugs.mysql.com/bug.php?id=58546))

* *Note `DELETE': delete. or *Note `UPDATE': update. statements
could fail if they used *Note `DATE': datetime. or *Note
`DATETIME': datetime. values with a year, month, or day part of
zero. (Bug#59173 http://bugs.mysql.com/bug.php?id=59173))

* The `ESCAPE' clause for the `LIKE' operator allows only
expressions that evaluate to a constant at execution time, but
aggregrate functions were not being rejected. (Bug#59149
http://bugs.mysql.com/bug.php?id=59149))

* *Note `mysqlslap': mysqlslap. failed to check for a `NULL' return
from *Note `mysql_store_result()': mysql-store-result. and crashed
trying to process the result set. (Bug#59109
http://bugs.mysql.com/bug.php?id=59109))

* In debug builds, `SUBSTRING_INDEX(FORMAT(...), FORMAT(...))' could
cause a server crash. (Bug#58371
http://bugs.mysql.com/bug.php?id=58371))

* When `mysqldadmin' was run with the `--sleep' and `--count'
options, it went into an infinite loop executing the specified
command. (Bug#58221 http://bugs.mysql.com/bug.php?id=58221))

* The *Note `mysql': mysql. client went into an infinite loop if the
standard input was a directory. (Bug#57450
http://bugs.mysql.com/bug.php?id=57450))

* When using `ExtractValue()' or `UpdateXML()', if the XML to be
read contained an incomplete XML comment, MySQL read beyond the
end of the XML string when processing, leading to a crash of the
server. (Bug#44332 http://bugs.mysql.com/bug.php?id=44332))


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


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




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