2011年5月11日

[installer 2793] mysql-5.5.12, 5.1.57

mysql-5.5.12, 5.1.57 出ています。

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

D.1.2. Changes in MySQL 5.5.12 (05 May 2011)
------------------------------------------------


Functionality added or changed:

* When invoked with the --auto-generate-sql option, mysqlslap
dropped the schema specified with the --create-schema option at
the end of the test run, which may have been unexpected by the
user. mysqlslap no longer drops the schema, but has a new
--create-and-drop-schema schema that both creates and drops a
schema. (Bug #58090, Bug #11765157)

Bugs fixed:

* InnoDB Storage Engine: Replication: Trying to update a column,
previously set to NULL, of an InnoDB table with no primary key
caused replication to fail with Can't find record in 'table' on
the slave. (Bug #11766865, Bug #60091)

* InnoDB Storage Engine: The server could halt if InnoDB
interpreted a very heavy I/O load for 15 minutes or more as an
indication that the server was hung. This change fixes the logic
that measures how long InnoDB threads were waiting, which
formerly could produce false positives. (Bug #11877216, Bug
#11755413, Bug #47183)

* InnoDB Storage Engine: With the setting lower_case_table_names=2,
inserts into InnoDB tables covered by foreign key constraints
could fail after a server restart. (Bug #11831040, Bug #60196,
Bug #60909)

* Replication: Using the --server-id option with mysqlbinlog could
cause format description log events to be filtered out of the
binary log, leaving mysqlbinlog unable to read the remainder of
the log. Now such events are always read without regard to the
value of this option.

As part of the the fix for this problem, mysqlbinlog now also
reads rotate log events without regard to the value of
--server-id. (Bug #11766427, Bug #59530)

* On Windows, the server rejected client connections if no DNS
server was available. (Bug #12325375)

* mysql_upgrade did not properly upgrade the authentication_string
column of the mysql.user table. (Bug #11936829)

* InnoDB invoked some zlib functions without proper
initialization. (Bug #11849231)

* Comparison of a DATETIME stored program variable and NOW() led to
an "Illegal mix of collations error" when
character_set_connection was set to utf8. (Bug #60625, Bug
#11926811)

* Selecting from a view for which the definition included a HAVING
clause failed with an error:

1356: View '...' references invalid table(s) or column(s)
or function(s) or definer/invoker of view lack rights to use them
(Bug #60295, Bug #11829681)

* CREATE TABLE syntax permits specification of a STORAGE
{DEFAULT|DISK|MEMORY} option. However, this value was not written
to the .frm file, so that a subsequent CREATE TABLE ... LIKE for
the table did not include that option.

Also, ALTER TABLE of a table that had a tablespace incorrectly
destroyed the tablespace. (Bug #60111, Bug #11766883, Bug #34047,
Bug #11747789)

* The server permitted max_allowed_packet to be set lower than
net_buffer_length, which does not make sense because
max_allowed_packet is the upper limit on net_buffer_length
values. Now a warning occurs and the value remains
unchanged. (Bug #59959, Bug #11766769)

* A missing variable initialization for Item_func_set_user_var
objects could cause an assertion to be raised. (Bug #59527, Bug
#11766424)

* When the server was started with the --skip-innodb option, it
initialized the have_innodb system variable to YES rather than
DISABLED. (Bug #59393, Bug #11766306)

* In Item_func_month::val_str(), a Valgrind warning for a too-late
NULL value check was corrected. (Bug #59166, Bug #11766126)

* In Item::get_date, a Valgrind warning for a missing NULL value
check was corrected. (Bug #59164, Bug #11766124)

* In extract_date_time(), a Valgrind warning for a missing
end-of-string check was corrected. (Bug #59151, Bug #11766112)

* In string context, the MIN() and MAX() functions did not take
into account the unsignedness of a BIGINT UNSIGNED argument. (Bug
#59132, Bug #11766094)

* In Item_func::val_decimal, a Valgrind warning for a missing NULL
value check was corrected. (Bug #59125, Bug #11766087)

* In Item_func_str_to_date::val_str, a Valgrind warning for an
uninitialized variable was corrected. (Bug #58154, Bug #11765216)

* An assertion could be raised in
Item_func_int_val::fix_num_length_and_dec() due to overflow for
geometry functions. (Bug #57900, Bug #11764994)

* With prepared statements, the server could attempt to send result
set metadata after the table had been closed. (Bug #56115, Bug
#11763413)

* With lower_case_table_names=2, resolution of objects qualified by
database names could fail. (Bug #50924, Bug #11758687)

* SHOW EVENTS did not always show events from the correct
database. (Bug #41907, Bug #11751148)


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

D.1.2. Changes in MySQL 5.1.57 (05 May 2011)
------------------------------------------------

Functionality added or changed:

* When invoked with the --auto-generate-sql option, mysqlslap
dropped the schema specified with the --create-schema option at
the end of the test run, which may have been unexpected by the
user. mysqlslap no longer drops the schema, but has a new
--create-and-drop-schema schema that both creates and drops a
schema. (Bug #58090, Bug #11765157)

* A new system variable, max_long_data_size, now controls the
maximum size of parameter values that can be sent with the
mysql_stmt_send_long_data() C API function. If not set at server
startup, the default is the value of the max_allowed_packet
system variable. This variable is deprecated. In MySQL 5.6, it is
removed and the maximum parameter size is controlled by
max_allowed_packet.

Bugs fixed:

* InnoDB Storage Engine: Replication: Trying to update a column,
previously set to NULL, of an InnoDB table with no primary key
caused replication to fail with Can't find record in 'table' on
the slave. (Bug #11766865, Bug #60091)

* InnoDB Storage Engine: The server could halt if InnoDB
interpreted a very heavy I/O load for 15 minutes or more as an
indication that the server was hung. This change fixes the logic
that measures how long InnoDB threads were waiting, which
formerly could produce false positives. (Bug #11877216, Bug
#11755413, Bug #47183)

* Replication: Using the --server-id option with mysqlbinlog could
cause format description log events to be filtered out of the
binary log, leaving mysqlbinlog unable to read the remainder of
the log. Now such events are always read without regard to the
value of this option.

As part of the the fix for this problem, mysqlbinlog now also
reads rotate log events without regard to the value of
--server-id. (Bug #11766427, Bug #59530)

* Partitioning: A problem with a previous fix for poor performance
of INSERT ON DUPLICATE KEY UPDATE statements on tables having
many partitions caused the handler function for reading a row
from a specific index to fail to store the ID of the partition
last used. This caused some statements to fail with Can't find
record errors. (Bug #59297, Bug #11766232)

* InnoDB invoked some zlib functions without proper
initialization. (Bug #11849231)

* Two unused test files in storage/ndb/test/sql contained incorrect
versions of the GNU Lesser General Public License. The files and
the directory containing them have been removed. (Bug #11810224)

See also Bug #11810156.

* Selecting from a view for which the definition included a HAVING
clause failed with an error:

1356: View '...' references invalid table(s) or column(s)
or function(s) or definer/invoker of view lack rights to use them
(Bug #60295, Bug #11829681)

* The server permitted max_allowed_packet to be set lower than
net_buffer_length, which does not make sense because
max_allowed_packet is the upper limit on net_buffer_length
values. Now a warning occurs and the value remains
unchanged. (Bug #59959, Bug #11766769)

* The server read one byte too many when trying to process an XML
string lacking a closing quote (') or double quote (") character
used as an argument for UpdateXML() or ExtractValue(). (Bug
#59901, Bug #11766725)

See also Bug #44332, Bug #11752979.

* Attempting to create a spatial index on a CHAR column longer than
31 bytes led to an assertion failure if the server was compiled
with safemutex support. (Bug #59888, Bug #11766714)

* Aggregation followed by a subquery could produce an incorrect
result. (Bug #59839, Bug #11766675)

* An incorrect character set pointer passed to my_strtoll10_mb2()
caused an assertion to be raised. (Bug #59648, Bug #11766519)

* A missing variable initialization for Item_func_set_user_var
objects could cause an assertion to be raised. (Bug #59527, Bug
#11766424)

* mysqldump did not quote database names in ALTER DATABASE
statements in its output, which could cause an error at reload
time for database names containing a dash. (Bug #59398, Bug
#11766310)

* In Item_func_month::val_str(), a Valgrind warning for a too-late
NULL value check was corrected. (Bug #59166, Bug #11766126)

* In Item::get_date, a Valgrind warning for a missing NULL value
check was corrected. (Bug #59164, Bug #11766124)

* In extract_date_time(), a Valgrind warning for a missing
end-of-string check was corrected. (Bug #59151, Bug #11766112)

* In string context, the MIN() and MAX() functions did not take
into account the unsignedness of a BIGINT UNSIGNED argument. (Bug
#59132, Bug #11766094)

* In Item_func::val_decimal, a Valgrind warning for a missing NULL
value check was corrected. (Bug #59125, Bug #11766087)

* In Item_func_str_to_date::val_str, a Valgrind warning for an
uninitialized variable was corrected. (Bug #58154, Bug #11765216)

* The code for PROCEDURE ANALYSE() had a missing DBUG_RETURN
statement, which could cause a server crash in debug builds. (Bug
#58140, Bug #11765202)

* An assertion could be raised in
Item_func_int_val::fix_num_length_and_dec() due to overflow for
geometry functions. (Bug #57900, Bug #11764994)

* An assertion could be raised if a statement that required a name
lock on a table (for example, DROP TRIGGER) executed concurrently
with an INFORMATION_SCHEMA query that also used the table. (Bug
#56541, Bug #11763784)

* For a client connected using SSL, the Ssl_cipher_list status
variable was empty and did not show the possible cipher
types. (Bug #52596, Bug #11760210)

* With lower_case_table_names=2, resolution of objects qualified by
database names could fail. (Bug #50924, Bug #11758687)

* A potential invalid memory access discovered by Valgrind was
fixed. (Bug #48053, Bug #11756169)

* Bitmap functions used in one thread could change bitmaps used by
other threads, causing an assertion to be raised. (Bug #43152,
Bug #11752069)

* SHOW EVENTS did not always show events from the correct
database. (Bug #41907, Bug #11751148)

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


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




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