2011年6月 2日

[installer 2816] mysql-5.5.13

mysql-5.5.13 出ています。

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

D.1.3. Changes in MySQL 5.5.13 (31 May 2011)
------------------------------------------------


Note
Very old (MySQL 4.0) clients are not working temporarily due to a
problem discovered after the release of MySQL 5.5.12. We are looking
at fixing the problem.

Bugs fixed:

* InnoDB Storage Engine: If the server crashed while an XA
transaction was prepared but not yet committed, the transaction
could remain in the system after restart, and cause a subsequent
shutdown to hang. (Bug #11766513, Bug #59641)

* InnoDB Storage Engine: Similar problem to the foreign key error
in bug #11831040 / 60196 / 60909, but with a different root cause
and occurring on Mac OS X. With the setting
lower_case_table_names=2, inserts into InnoDB tables covered by
foreign key constraints could fail after a server restart.

* Partitioning: The internal get_partition_set() function did not
take into account the possibility that a key specification could
be NULL in some cases. (Bug #12380149)

* Partitioning: When executing a row-ordered retrieval index merge,
the partitioning handler used memory from from that allocated for
the table, rather than that allocated to the query, causing table
object memory not to be freed until the table was closed. (Bug
#11766249, Bug #59316)

* Replication: A spurious error malformed binlog: it does not
contain any Format_description_log_event... was generated when
mysqlbinlog was invoked using --base64-output=decode-row and
--start-position=pos, where pos is a point in the binary log past
the format description log event. However, there is nothing
unsafe about not printing the format description log event, so
the error has been removed for this case. (Bug #12354268)

* Replication: Typographical errors appeared in the text of several
replication error messages. (The word “position” was misspelled
as "postion".) (Bug #11762616, Bug #55229)

* Assignments to NEW.var_name within triggers, where var_name had a
BLOB or TEXT type, were not properly handled and produced
incorrect results. (Bug #12362125)

* XA COMMIT could fail to clean up the error state if it discovered
that the current XA transaction had to be rolled
back. Consequently, the next XA transaction could raise an
assertion when it checked for proper cleanup of the previous
transaction. (Bug #12352846)

* An internal client macro reference was removed from the
client_plugin.h header file. This reference made the file
unusable. (Bug #60746, Bug #12325444)

* The server consumed memory for repeated invocation of some stored
procedures, which was not released until the connection
terminated. (Bug #60025, Bug #11848763)

* The server did not check for certain invalid out of order
sequences of XA statements, and these sequences raised an
assertion. (Bug #59936, Bug #11766752, Bug #12348348)

* With the conversion from GNU autotools to CMake for configuring
MySQL, the USE_SYMDIR preprocessor symbol was omitted. This
caused failure of symbolic links (described at Section 7.11.3.1,
"Using Symbolic Links"). (Bug #59408, Bug #11766320)

* The incorrect max_length value for YEAR values could be used in
temporary result tables for UNION, leading to incorrect
results. (Bug #59343, Bug #11766270)

* In Item_func_in::fix_length_and_dec(), a Valgrind warning for
uninitialized values was corrected. (Bug #59270, Bug #11766212)

* In ROUND() calculations, a Valgrind warning for uninitialized
memory was corrected. (Bug #58937, Bug #11765923)

* Valgrind warnings caused by comparing index values to an
uninitialized field were corrected. (Bug #58705, Bug #11765713)

* LOAD DATA INFILE errors could leak I/O cache memory. (Bug #58072,
Bug #11765141)

* For LOAD DATA INFILE, multibyte character sequences could be
pushed onto a stack too small to accommodate them. (Bug #58069,
Bug #11765139)

* Internal Performance Schema header files were unnecessarily
installed publicly. (Bug #53281)

* On Linux, the mysql client built using the bundled libedit did
not read ~/.editrc. (Bug #49967, Bug #11757855)

* The optimizer sometimes incorrectly processed HAVING clauses for
queries that did not also have an ORDER BY clause. (Bug #48916,
Bug #11756928)

* PROCEDURE ANALYZE() could leak memory for NULL results, and could
return incorrect results if used with a LIMIT clause. (Bug
#48137, Bug #11756242)

* With DISTINCT CONCAT(col,...) returned incorrect results when the
arguments to CONCAT() were columns with an integer data type
declared with a display width narrower than the values in the
column. (For example, if an INT(1) column contain 1111.) (Bug
#4082)

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


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




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