2011年3月22日

[installer 2726] mysql-5.5.10

mysql-5.5.10 出ています。

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

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


C API Notes:
* *Incompatible Change*: The shared library version of the client
library was increased to 18 to reflect ABI changes, and avoid
compatibility problems with the client library in MySQL 5.1. Note
that this is an incompatible change between 5.5.10 and earlier 5.5
versions, so client programs that use the 5.5 client library
should be recompiled against the 5.5.10 client library.

Functionality added or changed:

* The *Note `mysql_upgrade': mysql-upgrade, *Note `mysqlbinlog':
mysqlbinlog, *Note `mysqlcheck': mysqlcheck, *Note `mysqlimport':
mysqlimport, *Note `mysqlshow': mysqlshow, and *Note `mysqlslap':
mysqlslap. clients now have `--default-auth' and `--plugin-dir'
options for specifying which authentication plugin and plugin
directory to use. (Bug #58139)

* Boolean system variables can be enabled at run time by setting
them to the value `ON' or `OFF', but previously this did not work
at server startup. Now at startup such variables can be enabled by
setting them to `ON' or `TRUE', or disabled by setting them to
`OFF' or `FALSE'. Any other nonnumeric variable is invalid. (Bug
#46393) See also Bug #51631.

* Previously, for queries that were aborted due to sort problem, the
server wrote the message `Sort aborted' to the error log. Now the
server writes more information to provide a more specific message,
such as:

[ERROR] mysqld: Sort aborted: Out of memory (Needed 24 bytes)
[ERROR] mysqld: Out of sort memory,
consider increasing server sort buffer size
[ERROR] mysqld: Sort aborted: Out of sort memory,
consider increasing server sort buffer size
[ERROR] mysqld: Sort aborted: Incorrect number of arguments for
FUNCTION test.f1; expected 0, got 1

In addition, if the server was started with `--log-warnings=2',
the server write information about the host, user, and query.
(Bug #36022, Bug #11748358)

* *Note `mysqldump --xml': mysqldump. now displays comments from
column definitions. (Bug #13618)

Bugs fixed:

* *InnoDB Storage Engine*: Raised the number of I/O requests that
each AIO
http://dev.mysql.com/doc/innodb/1.1/en/glossary.html#glos_aio)
helper thread could process, from 32 to 256. The new limit applies
to Linux and Unix platforms; the limit on Windows remains 32.
(Bug #59472)

* *InnoDB Storage Engine*: *Note `InnoDB': innodb-storage-engine.
returned values for `rows examined' in the query plan that were
higher than expected. `NULL' values were treated in an
inconsistent way. The inaccurate statistics could trigger `false
positives' in combination with the `MAX_JOIN_SIZE' setting,
because the queries did not really examine as many rows as
reported. (Bug #30423)

* *Replication*: When using the statement-based logging format,
*Note `INSERT ON DUPLICATE KEY UPDATE': insert-on-duplicate. and
*Note `INSERT IGNORE': insert. statements affecting transactional
tables that did not fail were not written to the binary log if
they did not insert any rows. (With statement-based logging, all
successful statements should be logged, whether they do or do not
cause any rows to be changed.) (Bug #59338)

* *Replication*: Formerly, *Note `STOP SLAVE': stop-slave. stopped
the slave I/O thread first and then stopped the slave SQL thread;
thus, it was possible for the I/O thread to stop after replicating
only part of a transaction which the SQL thread was executing, in
which case--if the transaction could not be rolled back
safely--the SQL thread could hang.

Now, *Note `STOP SLAVE': stop-slave. stops the slave SQL thread
first and then stops the I/O thread; this guarantees that the I/O
thread can fetch any remaining events in the transaction that the
SQL thread is executing, so that the SQL thread can finish the
transaction if it cannot be rolled back safely. (Bug #58546)

* `DES_DECRYPT()' could crash if the argument was not produced by
`DES_ENCRYPT()'. (Bug #59632, Bug #11766505)

* The server and client did not always properly negotiate
authentication plugin names. (Bug #59453)

* `--autocommit=ON' did not work (it set the global `autocommit'
value to 0, not 1). (Bug #59432)

* A query of the following form returned an incorrect result, where
the values for COL_NAME in the result set were entirely replaced
with `NULL' values:

SELECT DISTINCT COL_NAME ... ORDER BY COL_NAME DESC;

(Bug #59308, Bug #11766241)

* *Note `SHOW PRIVILEGES': show-privileges. did not display a row
for the `PROXY' privilege. (Bug #59275)

* *Note `SHOW PROFILE': show-profile. could truncate source file
names or fail to show function names. (Bug #59273, Bug #11766214)

* *Note `DELETE': delete. or *Note `UPDATE': update. statements
could fail if they used *Note `DATE': datetime. or *Note
`DATETIME': datetime. values with a year, month, or day part of
zero. (Bug #59173)

* The `ESCAPE' clause for the `LIKE' operator allows only
expressions that evaluate to a constant at execution time, but
aggregate functions were not being rejected. (Bug #59149)

* Memory leaks detected by Valgrind, some of which could cause
incorrect query results, were corrected. (Bug #59110, Bug
#11766075)

* The `DEFAULT_CHARSET' and `DEFAULT_COLLATION' `CMake' options did
not work. (Bug #58991)

* Starting the server with the `--defaults-file=FILE_NAME' option,
where the file name had no extension, caused a server crash. (Bug
#58455, Bug #11765482)

* Outer joins with an empty table could produce incorrect results.
(Bug #58422)

* In debug builds, `SUBSTRING_INDEX(FORMAT(...), FORMAT(...))' could
cause a server crash. (Bug #58371)

* When *Note `mysqladmin': mysqladmin. was run with the `--sleep' and
`--count' options, it went into an infinite loop executing the
specified command. (Bug #58221)

* Some string manipulating SQL functions use a shared string object
intended to contain an immutable empty string. This object was
used by the SQL function `SUBSTRING_INDEX()' to return an empty
string when one argument was of the wrong datatype. If the string
object was then modified by the SQL function `INSERT()', undefined
behavior ensued. (Bug #58165, Bug #11765225)

* Parsing nested regular expressions could lead to recursion
resulting in a stack overflow crash. (Bug #58026, Bug #11765099)

* The fix for Bug#25192 caused `load_defaults()' to add an argument
separator to distinguish options loaded from configure files from
those provided on the command line, whether or not the application
needed it. (Bug #57953)

* The *Note `mysql': mysql. client went into an infinite loop if the
standard input was a directory. (Bug #57450)

* Outer joins on a unique key could return incorrect results. (Bug
#57034)

* The expression `CONST1 BETWEEN CONST2 AND FIELD' was optimized
incorrectly and produced incorrect results. (Bug #57030, Bug
#11764215)

* Some RPM installation scripts used a hardcoded value for the data
directory, which could result in a failed installation for users
who have a nonstandard data directory location. The same was true
for other configuration values such as the PID file name. (Bug
#56581, Bug #11763817)

* On FreeBSD and OpenBSD, the server incorrectly checked the range
of the system date, causing legal values to be rejected. (Bug
#55755, Bug #11763089)

* Sorting using `ORDER BY AVG(DISTINCT DECIMAL_COL)' caused a server
crash or incorrect results. (Bug #52123, Bug #11759784)

* When using `ExtractValue()' or `UpdateXML()', if the XML to be
read contained an incomplete XML comment, MySQL read beyond the
end of the XML string when processing, leading to a crash of the
server. (Bug #44332)

* `DATE_ADD()' and `DATE_SUB()' return a string if the first
argument is a string, but incorrectly returned a binary string.
Now they return a character string with a collation of
`connection_collation'. (Bug #31384, Bug #11747221)

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


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




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