MySQL Upgrade 5.5.28

InnoDB: Certain information_schema tables originally introduced in MySQL 5.6
are now also available in MySQL 5.5 and MySQL 5.1 (Bug #13113026)

InnoDB: When a SELECT … FOR UPDATE, UPDATE, or other SQL statement
scanned rows in an InnoDB table using a < or <= operator in a WHERE clause,
the next row after the affected range could also be locked. (Bug #11765218)
Partitioning: When used with a table having multiple columns in its primary key,
but partitioned by KEY using a column that was not part of the primary key
as the partitioning column, a query using an aggregate function and DISTINCT
such as SELECT SUM(DISTINCT pk_column_1) FROM table WHERE pk_column_2 = constant
was not handled correctly. (Bug #14495351)
Partitioning: For tables using PARTITION BY HASH or PARTITION BY KEY,
when the partition pruning mechanism encountered a multi-range list or
inequality using a column from the partitioning key, it continued with the next
partitioning column and tried to use it for pruning, even if the previous column
could not be used. (Bug #14342883)
Partitioning: The buffer for the row currently read from each partition used for
sorted reads was allocated on open and freed only when the partitioning handler
was closed or destroyed. For SELECT statements on tables with many partitions and
large rows, this could cause the server to use excessive amounts of memory.(Bug #13025132)
Replication: On 64-bit Windows platforms, values greater than 4G for the max_binlog_cache_size
and max_binlog_stmt_cache_size system variables were truncated to 4G.(Bug #13961678)
Replication: In master-master replication with --log-slave-updates enabled, setting a user
variable and then performing inserts using this variable caused the Exec_master_log_position
column in the output of SHOW SLAVE STATUS not to be updated. (Bug #13596613)
mysqlhotcopy failed for databases containing views. (Bug #62472, Bug #13006947, Bug #12992993)
Adding a LIMIT clause to a query containing GROUP BY and ORDER BY could cause the
optimizer to choose an incorrect index for processing the query, and return more rows
than required. (Bug #54599, Bug #11762052)
mysqlbinlog did not accept input on the standard input when the standard input was a pipe.
(Bug #49336, Bug #11757312)
その他、数件のBugFixあり