2012年1月13日

[installer 3073] mysql-5.1.61, 5.5.20

mysql-5.1.61, 5.5.20 出ています。

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

D.1.1. Changes in MySQL 5.1.61 (10 January 2012)
------------------------------------------------


*Bugs Fixed*

* *InnoDB Storage Engine*: Issuing INSERT...ON DUPLICATE KEY
statements for InnoDB tables from concurrent threads could cause
a deadlock, particularly with the INSERT...ON DUPLICATE KEY
UPDATE form. The fix avoids deadlocks caused by the same row
being accessed by more than one transaction. Deadlocks could
still occur when multiple rows are inserted and updated
simultaneously by different transactions in inconsistent order;
those types of deadlocks require the standard error handling on
the application side, of re-trying the transaction. (Bug
#11759688, Bug #52020)

* An incorrect InnoDB assertion could cause the server to
halt. This issue only affected debug builds. The assertion
referenced the source file btr0pcur.ic and the variable
cursor->pos_state. (Bug #13358468)

* The handle_segfault() signal-handler code in mysqld could itself
crash due to calling unsafe functions. (Bug #54082, Bug
#11761576)

* ARCHIVE tables with NULL columns could cause server crashes or
become corrupt under concurrent load. (Bug #51252, Bug #11758979)

* Enabling myisam_use_mmap could cause the server to crash. (Bug
#48726, Bug #11756764)

* Concurrent access to ARCHIVE tables could cause corruption. (Bug
#42784, Bug #11751793)


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

D.1.1. Changes in MySQL 5.5.20 (10 January 2012)
------------------------------------------------
*Functionality Added or Changed*

* A new server option, --slow-start-timeout, controls the Windows
service control manager's service start timeout. The value is the
maximum number of milliseconds that the service control manager
waits before trying to kill the MySQL service during startup. The
default value is 15000 (15 seconds). If the MySQL service takes
too long to start, you may need to increase this value. A value
of 0 means there is no timeout. (Bug #45546, Bug #11754011)

*Bugs Fixed*

* *Important Change*: *Replication*: Setting an empty user in a
CHANGE MASTER TO statement caused an invalid internal result and
is no longer permitted. Trying to use MASTER_USER='' or setting
MASTER_PASSWORD while leaving MASTER_USER unset causes the
statement to fail with an error. (Bug #13427949)

* *Important Change*: *Replication*: Moving the binary log file,
relay log file, or both files to a new location, then restarting
the server with a new value for --log-bin, --relay-log, or both,
caused the server to abort on start. This was because the entries
in the index file overrode the new location. In addition, paths
were calculated relative to datadir (rather than to the --log-bin
or --relay-log values).

* *Important Change*: *Replication*: Moving the binary log file,
relay log file, or both files to a new location, then restarting
the server with a new value for --log-bin, --relay-log, or both,
caused the server to abort on start. This was because the entries
in the index file overrode the new location. In addition, paths
were calculated relative to datadir (rather than to the --log-bin
or --relay-log values).

* *InnoDB Storage Engine*: When doing a live downgrade from MySQL
5.6.4 or later, with innodb_page_size set to a value other than
16384, now the earlier MySQL version reports that the page size
is incompatible with the older version, rather than crashing or
displaying a “corruption” error. (Bug #13116225)

* *InnoDB Storage Engine*: Issuing INSERT...ON DUPLICATE KEY
statements for InnoDB tables from concurrent threads could cause
a deadlock, particularly with the INSERT...ON DUPLICATE KEY
UPDATE form. The fix avoids deadlocks caused by the same row
being accessed by more than one transaction. Deadlocks could
still occur when multiple rows are inserted and updated
simultaneously by different transactions in inconsistent order;
those types of deadlocks require the standard error handling on
the application side, of re-trying the transaction. (Bug
#11759688, Bug #52020)

* An incorrect InnoDB assertion could cause the server to
halt. This issue only affected debug builds. The assertion
referenced the source file btr0pcur.ic and the variable
cursor->pos_state. (Bug #13358468)

* Locale information for FORMAT() function instances was lost in
view definitions. (Bug #63020, Bug #13344643)

* The handle_segfault() signal-handler code in mysqld could itself
crash due to calling unsafe functions. (Bug #54082, Bug
#11761576)

* Enabling myisam_use_mmap could cause the server to crash. (Bug
#48726, Bug #11756764)

* Concurrent access to ARCHIVE tables could cause corruption. (Bug
#42784, Bug #11751793)

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


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




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