SELECT using a range
WHERE condition with an
BY on a partitioned table caused a server crash.
Row-based replication failed with nonpartitioned
MyISAM tables having no indexes.
With statement-based binary logging format and a transaction
isolation level of
COMMITTED or stricter,
printed an error because statement-based logging might lead to
inconsistency between master and slave databases. However, this
error was printed even when binary logging was not enabled (in
which case, no such inconsistency can occur).
CHECK TABLE ...
FOR UPGRADE statement did not check for incompatible
collation changes made in MySQL 5.1.24 (Bug#27877). This also
affects mysqlcheck and
mysql_upgrade, which cause that statement to
be executed. See Section 2.12.3, “Checking Whether Table Indexes Must Be Rebuilt”.
Prior to this fix, a binary upgrade (performed without dumping
tables with mysqldump before the upgrade and
reloading the dump file after the upgrade) would corrupt tables
that have indexes that use the
ucs2_general_ci collation for columns that
'ß' LATIN SMALL LETTER SHARP S
(German). After the fix,
CHECK TABLE ... FOR
UPGRADE properly detects the problem and warns about
tables that need repair.
However, the fix is not backward compatible and can result in a downgrading problem under these circumstances:
Some recent releases for Solaris 10 were built on Solaris 10 U5,
which included a new version of
that does not work on U4 or earlier. To correct this, Solaris 10
builds now are created on machines that do not have that
libnsl.so, so that they will work
on Solaris 10 installations both with and without the upgraded
XA transaction rollbacks could result in corrupted transaction states and a server crash. (Bug#28323)