2011年7月 8日

[installer 2869] mysql-5.5.14, 5.1.58

mysql-5.5.14, 5.1.58 出ています。

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

D.1.3. Changes in MySQL 5.5.14 (05 July 2011)
------------------------------------------------


Functionality added or changed:

* CMake configuration support on Linux now provides a boolean
ENABLE_GCOV option to control whether to include support for
gcov. (Bug #12549572)

* InnoDB now permits concurrent reads while creating a secondary
index. (Bug #11853126)

See also Bug #11751388, Bug #11784056, Bug #11815600.

* Client programs now display more information for SSL errors to
aid in diagnosis and debugging of connection problems. (Bug
#21287, Bug #11745920)

* In the audit plugin interface, the event_class member was removed
from the mysql_event_general structure and the calling sequence
for the notification function changed. Originally, the second
argument was a pointer to the event structure. The function now
receives this information as two arguments: an event class number
and a pointer to the event. Corresponding to these changes,
MYSQL_AUDIT_INTERFACE_VERSION was increased to 0x0300.

The plugin_audit.h header file, and the NULL_AUDIT example plugin
in the plugin/audit_null directory have been modified per these
changes. See Section 21.2.4.7, “Writing Audit Plugins”.

Bugs fixed:

* Replication: A mistake in thread cleanup could cause a
replication master to crash. (Bug #12578441)

* Replication: When using row-based replication and attribute
promotion or demotion (see Section 15.4.1.6.2, “Replication of
Columns Having Different Data Types”), memory allocated
internally for conversion of BLOB columns was not freed
afterwards. (Bug #12558519)

* Adding support for Windows authentication to libmysql introduced
a link dependency on the system Secur32 library. The Microsoft
Visual C++ link information was modified to pull in this library
automatically. (Bug #12612143)

* In some cases, memory allocated for
Query_tables_list::sroutines() was not freed properly. (Bug
#12429877)

* After the fix for Bug#11889186, MAKEDATE() arguments with a year
part greater than 9999 raised an assertion. (Bug #12403504)

* An assertion could be raised due to a missing NULL value check in
Item_func_round::fix_length_and_dec(). (Bug #12392636)

* An assertion could be raised during two-phase commits if the
binary log was used as the transaction coordinator log. (Bug
#12346411)

* A problem introduced in 5.5.11 caused very old (MySQL 4.0)
clients to be unable to connect to the server. (Bug #61222, Bug
#12563279)

* Using CREATE EVENT IF NOT EXISTS for an event that already
existed and was enabled caused multiple instances of the event to
run. (Bug #61005, Bug #12546938)

* An embedded client would abort rather than issue an error message
if it issued a TEE command (\T file_name) and the directory
containing the file did not exist. This occurred because the
wrong error handler was called. (Bug #57491, Bug #11764633)

* On some platforms, the Incorrect value: xxx for column yyy at row
zzz error produced by LOAD DATA INFILE could have an incorrect
value of zzz. (Bug #46895, Bug #11755168)

* An attempt to install nonexistent files during installation was
corrected. (Bug #43247, Bug #11752142)

* On FreeBSD 64-built builds of the embedded server, exceptions
were not prevented from propagating into the embedded
application. (Bug #38965, Bug #11749418)


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

D.1.2. Changes in MySQL 5.1.58 (Not yet released)
------------------------------------------------

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)

* Partitioning: When executing a row-ordered retrieval index merge,
the partitioning handler used memory 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: 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), a spurious error of the type shown here was generated:

malformed binlog: it does not contain any
Format_description_log_event...

However, since there is nothing unsafe about not printing the
format description log event, 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)

* After the fix for Bug#11889186, MAKEDATE() arguments with a year
part greater than 9999 raised an assertion. (Bug #12403504)

* An assertion could be raised due to a missing NULL value check in
Item_func_round::fix_length_and_dec(). (Bug #12392636)

* In debug builds on Solaris, an assertion was raised if a reverse
IP lookup with gethostbyaddr_r() failed. (Bug #12377872)

* MySQL did not build if configured with both --with-debug and
--with-libedit. (Bug #12329909)

* A problem introduced in 5.1.57 caused very old (MySQL 4.0)
clients to be unable to connect to the server. (Bug #61222, Bug
#12563279)

* Using CREATE EVENT IF NOT EXISTS for an event that already
existed and was enabled caused multiple instances of the event to
run. (Bug #61005, Bug #12546938)

* 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)

* An embedded client would abort rather than issue an error message
if it issued a TEE command (\T file_name) and the directory
containing the file did not exist. This occurred because the
wrong error handler was called. (Bug #57491, Bug #11764633)

* In debug builds, Field_new_decimal::store_value() was subject to
buffer overflows. (Bug #55436, Bug #11762799)

* 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)

* On some platforms, the Incorrect value: xxx for column yyy at row
zzz error produced by LOAD DATA INFILE could have an incorrect
value of zzz. (Bug #46895, Bug #11755168)

* In MySQL 5.1 and up, if a table had triggers that used syntax
supported in 5.0 but not 5.1, the table became unavailable. Now
the table is marked as having broken triggers. (Bug #45235, Bug
#11753738)

* An attempt to install nonexistent files during installation was
corrected. (Bug #43247, Bug #11752142)

* On FreeBSD 64-built builds of the embedded server, exceptions
were not prevented from propagating into the embedded
application. (Bug #38965, Bug #11749418)

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


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




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