2009年8月 4日

[installer 2025] mysql-5.1.37

mysql-5.1.37 出ています。

☆ mysql-5.1.37
http://www.mysql.com/
http://dev.mysql.com/downloads/mysql/5.1.html
ftp://ftp.iij.ad.jp/pub/db/mysql/Downloads/MySQL-5.1/mysql-5.1.37.tar.gz
http://ftp.iij.ad.jp/pub/db/mysql/Downloads/MySQL-5.1/mysql-5.1.37.tar.gz
http://mirror.mysql-partners-jp.biz/Downloads/MySQL-5.1/mysql-5.1.37.tar.gz


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

Functionality added or changed:

* *Important Change*: *Replication*: *Note `RESET MASTER':
reset-master. and *Note `RESET SLAVE': reset-slave. now reset the
values shown for `Last_IO_Error', `Last_IO_Errno',
`Last_SQL_Error', and `Last_SQL_Errno' in the output of *Note
`SHOW SLAVE STATUS': show-slave-status. (Bug#44270
http://bugs.mysql.com/44270)) See also Bug#34654
http://bugs.mysql.com/34654).

Bugs fixed:

* *Important Change*: *Replication*: When using `STATEMENT' or
`MIXED' binary logging format, a statement that changes both
non-transactional and transactional tables must be written to the
binary log whenever there are changes to non-transactional tables.
This means that the statement goes into the binary log even when
the changes to the transactional tables fail. In particular, in
the event of a failure such statement is annotated with the error
number and wrapped inside a pair of *Note `BEGIN': commit. and
*Note `ROLLBACK': commit. statements.

On the slave, while applying the statement, it is expected that
the same failure and the rollback prevent the transactional
changes from persisting. However, statements that fail due to
concurrency issues such as deadlocks and timeouts are logged in
the same way, causing the slave to stop since the statements are
applied sequentially by the SQL thread.

To address this issue, we ignore concurrency failures on the
slave. Specifically, the following failures are now ignored:
ER_LOCK_WAIT_TIMEOUT, ER_LOCK_DEADLOCK, and ER_XA_RBDEADLOCK.
(Bug#44581 http://bugs.mysql.com/44581))

* *Partitioning*: Truncating a partitioned `MyISAM' table did not
reset the `AUTO_INCREMENT' value. (Bug#35111
http://bugs.mysql.com/35111))

* *Replication*: The *Note `SHOW SLAVE STATUS': show-slave-status.
connection thread competed with the slave SQL thread for use of
the error message buffer. As a result, the connection thread
sometimes received incomplete messages. This issue was uncovered
with `valgrind' when message strings were passed without `NULL'
terminators, causing the error `Conditional jump or move depends
on uninitialised value(s)'. (Bug#45511
http://bugs.mysql.com/45511)) See also Bug#43076
http://bugs.mysql.com/43076).

* *Replication*: Large transactions and statements could corrupt the
binary log if the size of the cache (as set by
`max_binlog_cache_size') was not large enough to store the changes.

Now, for transactions that do not fit into the cache, the
statement is not logged, and the statement generates an error
instead.

For non-transactional changes that do not fit into the cache, the
statement is also not logged -- an incident event is logged after
committing or rolling back any pending transaction, and the
statement then raises an error.

*Note*:

If a failure occurs before the incident event is written the
binary log, the slave does not stop, and the master does not
report any errors.

(Bug#43929 http://bugs.mysql.com/43929)) See also Bug#37148
http://bugs.mysql.com/37148).

* *Replication*: The `--database' option for *Note `mysqlbinlog':
mysqlbinlog. was ignored when using the row-based logging format.
(Bug#42941 http://bugs.mysql.com/42941))

* *Replication*: Shutting down the server while executing `FLUSH
LOGS', *Note `CHANGE MASTER TO': change-master-to, or *Note `STOP
SLAVE': stop-slave. could sometimes cause *Note `mysqld': mysqld.
to crash. (Bug#38240 http://bugs.mysql.com/38240))

* *Replication*: When reading a binary log that was in use by a
master or that had not been properly closed (possibly due to a
crash), the following message was printed: `Warning: this binlog
was not closed properly. Most probably mysqld crashed writing it'.
This message did not take into account the possibility that the
file was merely in use by the master, which caused some users
concern who were not aware that this could happen.

To make this clear, the original message has been replaced with
`Warning: this binlog is either is use or was not closed properly'.
(Bug#34687 http://bugs.mysql.com/34687))

* The server crashed if evaluation of `GROUP_CONCAT(... ORDER BY)'
required allocation of a sort buffer but allocation failed.
(Bug#46080 http://bugs.mysql.com/46080))

* The server crashed for attempts to use *Note `REPLACE': replace. or
*Note `INSERT ... ON DUPLICATE KEY UPDATE': insert. with a view
defined using a join. (Bug#45806 http://bugs.mysql.com/45806))

* There was a race condition when changing
`innodb_commit_concurrency' at runtime to the value `DEFAULT'.
(Bug#45749 http://bugs.mysql.com/45749)) See also Bug#42101
http://bugs.mysql.com/42101).

* If an error occurred during the creation of a table (for example,
the table already existed) having an `AUTO_INCREMENT' column and a
`BEFORE' trigger that used the *Note `INSERT ... SELECT':
insert-select. construct, an internal flag was not reset properly.
This led to a crash the next time that the table was opened again.
(Bug#44653 http://bugs.mysql.com/44653))

* For queries with a sufficient number of subqueries in the `FROM'
clause of this form:

SELECT * FROM (SELECT 1) AS t1,
(SELECT 2) AS t2,
(SELECT 3) AS t3, ...

The query failed with a `Too high level of nesting for select'
error, as those the query had this form:

SELECT * FROM (SELECT 1 FROM (SELECT 2 FROM (SELECT 3 FROM ...

(Bug#44156 http://bugs.mysql.com/44156))

* Renaming a column that appeared in a foreign key definition did
not update the foreign key definition with the new column name.
(Bug#21704 http://bugs.mysql.com/21704))

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


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




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