InnoDB Plugin Notes
InnoDB Plugin has been upgraded to version
1.0.10. This version is considered of General Availability (GA)
In this release, the
InnoDB Plugin is
included in source and binary distributions, except RHEL3,
RHEL4, SuSE 9 (x86, x86_64, ia64), generic Linux RPM packages,
and any builds produced with the
compiler. It also does not work for FreeBSD 6 and HP-UX or for
Linux on generic ia64.
Functionality Added or Changed
The mechanism that checks if there is enough space for redo logs
was improved, reducing the chance of encountering this message:
ERROR: the age of the last checkpoint is
x, which exceeds the log group
Security Fix; InnoDB:
After changing the values of the
parameters, DDL statements could cause a server crash.
(Bug #55039, CVE-2010-3676)
INFILE did not check for SQL errors and sent an OK
packet even when errors were already reported. Also, an assert
related to client/server protocol checking in debug servers
sometimes was raised when it should not have been.
(Bug #52512, CVE-2010-3683)
EXPLAIN with queries of the
SELECT ... UNION ... ORDER BY (SELECT ... WHERE
...) could cause a server crash.
(Bug #52711, CVE-2010-3682)
The server could crash if there were alternate reads from two
indexes on a table using the
(Bug #54007, CVE-2010-3681)
InnoDB tables with nullable columns
could cause a server crash.
(Bug #54044, CVE-2010-3680)
A malformed argument to the
BINLOG statement could result in
Valgrind warnings or a server crash.
(Bug #54393, CVE-2010-3679)
Incorrect handling of
NULL arguments could
lead to a crash for
CASE operations when
NULL arguments were either passed explicitly
as arguments (for
implicitly generated by the
(Bug #54477, CVE-2010-3678)
Joins involving a table with a unique
SET column could cause a server
(Bug #54575, CVE-2010-3677)
Security Fix: A security bug was fixed. (Bug #52315)
Security Fix: A security bug was fixed. (Bug #53933)
Performing large numbers of
TABLE statements caused excessive memory use.
Fast index creation in the
could fail, leaving the new secondary index corrupted.
InnoDB could issue an incorrect message on
startup, if tables were created under the setting
innodb_file_per_table=ON. The message was of
InnoDB: Warning: allocated tablespace
you encounter this message after upgrading, create an
n, old maximum was 0
InnoDB table with
innodb_file_per_table = ON and restart the
server. The message should not be displayed any more. If you
continue to encounter this message, or if you get it and haven't
used a version without this fix, you might have corruption in
your shared tablespace. If so, back up and reload your data.
ALTER TABLE statement could
InnoDB compressed table (with
row_format=compressed) back to an
uncompressed table (with
Some combinations of
SELECT FOR UPDATE statements could fail with
errors about locks, or incorrectly release a row lock during a
Replication: Two related issues involving temporary tables and transactions were introduced by a fix made in MySQL 5.1.37:
When a temporary table was created or dropped within a
transaction, any failed statement that following the
TEMPORARY TABLE or
TABLE statement triggered a rollback, which caused
the slave to diverge from the master.
TEMPORARY TABLE ... SELECT * FROM ... statement
was executed within a transaction in which only tables using
transactional storage engines were used and the transaction
was rolled back at the end, the changes—including the
creation of the temporary table—were not written to
the binary log.
The current fix restores the correct behavior in both of these cases. (Bug #53560)
References: This bug was introduced by Bug #43929.
CURRENT_USER was used to supply
the name and host of the affected user or of the definer in any
of the statements
ALTER EVENT, the reference to
CURRENT_USER was not expanded
when written to the binary log. This resulted in
CURRENT_USER being expanded to
the user and host of the slave SQL thread on the slave, thus
breaking replication. Now
CURRENT_USER are expanded prior
to being written to the binary log in such cases, so that the
correct user and host are referenced on both the master and the
When using unique keys on
NULL columns in
row-based replication, the slave sometimes chose the wrong row
when performing an update. This happened because a table having
a unique key on such a column could have multiple rows
NULL for the column used by the
unique key, and the slave merely picked the first row containing
NULL in that column.
could in some circumstances crash the server. This occurred
because the I/O thread could concurrently access the relay log
I/O cache while another thread was performing the
which closes and reopens the relay log and, while doing so,
initializes (or re-initializes) its I/O cache. This could cause
problems if some other thread (in this case, the I/O thread) is
accessing it at the same time.
Now the thread performing the
takes a lock on the relay log before actually flushing it.
References: See also Bug #50364.
make_binary_distribution target to
make could fail on some platforms because the
lines generated were too long for the shell.
mysqld could fail during execution when using SSL. (Bug #34236)
Builds of the embedded mysqld failed due to a
missing element of the
(Bug #53908, Bug #53912)
The definition of the
MY_INIT macro in
my_sys.h included an extraneous semicolon,
which could cause compilation failure.
Valgrind warnings in the
compare_record() function were corrected.
The server could crash with an out of memory error when trying
to parse a query that was too long to fit in memory. Now the
parser rejects such queries with an
Lock_time value in the slow query log was
negative for stored routines.
A client with automatic reconnection enabled saw the error
Lost connection to MySQL server during
query if the connection was lost between the
mysql_stmt_execute() C API
mysql_stmt_errno() returned 0,
not the corresponding error number 2013.
The server failed to disregard sort order for some zero-length tuples, leading to an assertion failure. (Bug #54459)
The default value of
myisam_max_extra_sort_file_size could be
higher than the maximum accepted value, leading to warnings upon
the server start.
If a session tried to drop a database containing a table opened
HANDLER in another session,
ALTER) executed by that session produced a
index_merge for join tables other than
the first table used excessive memory.
The results of some
ORDER BY ... DESC queries
were sorted incorrectly.
Index Merge between three indexes could
return incorrect results.
A signal-handler redefinition for
removed. The redefinition could cause the server to encounter a
kernel deadlock on Solaris when there are many active threads.
Other POSIX platforms might also be affected.
Inconsistent checking of the relationship between
SHOW statements and
INFORMATION_SCHEMA queries caused such
queries to fail sometimes.
The behavior of the RPM upgrade installation has changed. During
an upgrade installation using the RPM packages, if the MySQL
server is running when the upgrade occurs, the server is
stopped, the upgrade occurs, and server is restarted. If the
server is not already running when the RPM upgrade occurs, the
server is not started at the end of the upgrade. The boot
scripts for MySQL are installed in the appropriate directories
/etc, so the MySQL server will be
restarted automatically at the next machine reboot.