2011年9月20日

[installer 2957] mysql-5.5.16, 5.1.59

mysql-5.5.16, 5.1.59 出ています。

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

D.1.1 Changes in MySQL 5.5.16 (15 September 2011)
------------------------------------------------


*Functionality Added or Changed*

* *Important Change*: *Replication*: The *Note `RESET SLAVE':
reset-slave. statement has been extended with an `ALL' keyword. In
addition to deleting the `master.info', `relay-log.info', and all
relay log files, *Note `RESET SLAVE ALL': reset-slave. also clears
all connection information otherwise held in memory following
execution of *Note `RESET SLAVE': reset-slave. (Bug #11809016)

* A new utility, *Note `mysql_plugin': mysql-plugin, enables MySQL
administrators to manage which plugins a MySQL server loads. It
provides an alternative to manually specifying the `--plugin-load'
option at server startup or using the *Note `INSTALL PLUGIN':
install-plugin. and *Note `UNINSTALL PLUGIN': uninstall-plugin.
statements at runtime. See *Note mysql-plugin::.

*Bugs Fixed*

* *InnoDB Storage Engine*: The `random read-ahead
http://dev.mysql.com/doc/innodb/1.1/en/glossary.html#glos_read_ahead)'
feature that was removed from the `InnoDB' Plugin is now available
again. Because it is only helpful for certain workloads, it is
turned off by default. To turn it on, enable the
`innodb_random_read_ahead' configuration option. Because this
feature can improve performance in some cases and reduce
performance in others, before relying on this setting, benchmark
both with and without the setting enabled. (Bug #12356373)

* The metadata locking subsystem added too much overhead for
`INFORMATION_SCHEMA' queries that were processed by opening only
`.frm' or `.TRG' files and had to scan many tables. For example,
`SELECT COUNT(*) FROM INFORMATION_SCHEMA.TRIGGERS' was affected.
(Bug #12828477)

* Compilation failed on Mac OS X 10.7 (Lion) with a warning:
`Implicit declaration of function 'pthread_init'' (Bug #12779790)

* With profiling disabled or not compiled in, `set_thd_proc_info()'
unnecessarily checked file name lengths. (Bug #12756017)

* A `DBUG_ASSERT' added by Bug #11792200 was overly aggressive in
raising assertions. (Bug #12537160)

* *Note `CHECK TABLE': check-table. and *Note `REPAIR TABLE':
repair-table. failed to find problems with *Note `MERGE':
merge-storage-engine. tables that had underlying tables missing or
with the wrong storage engine. Issues were reported only for the
first underlying table. (Bug #11754210)

* *Replication*: Processing of corrupted table map events could
cause the server to crash. This was especially likely if the
events mapped different tables to the same identifier, such as
could happen due to Bug#56226.

Now, before applying a table map event, the server checks whether
the table has already been mapped with different settings, and if
so, an error is raised and the slave SQL thread stops. If it has
been mapped with the same settings, or if the table is set to be
ignored by filtering rules, there is no change in behavior: the
event is skipped and IDs are not checked. (Bug #44360, Bug
#11753004) See also Bug #11763509.

* For a `lower_case_table_names' value of 1 or 2 and a database
having a mixed-case name, calling a stored function using a fully
qualified name including the database name failed. (Bug #60347,
Bug #11840395)

* Previously, Performance Schema table columns that held byte counts
were `BIGINT UNSIGNED'. These were changed to `BIGINT' (signed).
This makes it easier to perform calculations that compute
differences between columns. (Bug #59631, Bug #11766504)

* The embedded server crashed when `argc = 0'. (Bug #57931, Bug
#12561297)

* The `mysql_affected_rows()' C API function returned 3 (instead of
2) for *Note `INSERT ... ON DUPLICATE KEY UPDATE':
insert-on-duplicate. statements where there was a duplicated key
value. (Bug #46675, Bug #11754979)

* Upgrades using an RPM package recreated the `test' database, which
is undesirable when the DBA had removed it. (Bug #45415, Bug
#11753896)


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

D.1.1 Changes in MySQL 5.1.59 (15 September 2011)
------------------------------------------------

*Functionality Added or Changed*

* If the `--with-ndbcluster' option is given to the `configure'
script, it now produces a warning that the version of MySQL
Cluster included in 5.1 is no longer maintained. (The separate
MySQL Cluster distribution should be used instead.) (Bug #49093,
Bug #11757091)

*Bugs Fixed*

* *InnoDB Storage Engine*: The "random read-ahead" feature that was
removed from the InnoDB Plugin is now available again. Because it
is only helpful for certain workloads, it is turned off by
default. To turn it on, enable the innodb_random_read_ahead
configuration option. Because this feature can improve
performance in some cases and reduce performance in others,
before relying on this setting, benchmark both with and without
the setting enabled. (Bug #12356373)

* *Partitioning*: Auto-increment columns of partitioned tables were
checked even when they were not being written to. In debug builds,
this could lead to a server crash. (Bug #11765667, Bug #58655)

* The option-parsing code for empty strings leaked memory. (Bug
#12589928)

* *Replication*: Processing of corrupted table map events could
cause the server to crash. This was especially likely if the
events mapped different tables to the same identifier, such as
could happen due to Bug#56226.

Now, before applying a table map event, the server checks whether
the table has already been mapped with different settings, and if
so, an error is raised and the slave SQL thread stops. If it has
been mapped with the same settings, or if the table is set to be
ignored by filtering rules, there is no change in behavior: the
event is skipped and IDs are not checked. (Bug #44360, Bug
#11753004) See also Bug #11763509.

* *Note `ALTER TABLE {MODIFY|CHANGE} ... FIRST': alter-table. did
nothing except rename columns if the old and new versions of the
table had exactly the same structure with respect to column data
types. As a result, the mapping of column name to column data was
incorrect. The same thing happened for *Note `ALTER TABLE DROP
COLUMN ... ADD COLUMN': alter-table. statements intended to
produce a new version of the table with exactly the same structure
as the old version. (Bug #61493, Bug #12652385)

* For a `lower_case_table_names' value of 1 or 2 and a database
having a mixed-case name, calling a stored function using a fully
qualified name including the database name failed. (Bug #60347,
Bug #11840395)

* Previously, Performance Schema table columns that held byte counts
were `BIGINT UNSIGNED'. These were changed to `BIGINT' (signed).
This makes it easier to perform calculations that compute
differences between columns. (Bug #59631, Bug #11766504)

* For *Note `MyISAM': myisam-storage-engine. tables, attempts to
insert incorrect data into an indexed `GEOMETRY' column could
result in table corruption. (Bug #57323, Bug #11764487)

* A race condition between loading a stored routine using the name
qualified by the database name and dropping that database resulted
in a spurious error message: `The table mysql.proc is missing,
corrupt, or contains bad data' (Bug #47870, Bug #11756013)

* Upgrades using an RPM package recreated the `test' database, which
is undesirable when the DBA had removed it. (Bug #45415, Bug
#11753896)

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


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




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