InnoDB has been upgraded to version 1.1. This
version is considered of Beta quality.
debuginfo RPM packages are no longer being
built or published.
Functionality Added or Changed
InnoDB now has a
variable that can be disabled at startup if there is a problem
with the asynchronous I/O subsystem in the OS. This variable
applies to Linux systems only, where the MySQL server now has a
dependency on the
The redo scan during
InnoDB recovery used
excessive CPU. The efficiency of this scan was improved,
significantly speeding up crash recovery.
(Bug #49535, Bug #29847)
InnoDB page-freeing operations were made
faster for compressed blocks, speeding up
DROP TABLE, and other operations
on compressed tables that free compressed blocks. One symptom of
the older behavior could be 100% CPU use during these
The AIX implementation of
InnoDB: The limit of 1023 concurrent data-modifying transactions has been raised. The limit is now 128 × 1023 concurrent transactions that generate undo records. You can remove any workarounds that require changing the proper structure of your transactions, such as committing more frequently or delaying DML operations to the end of a transaction. See Better Scalability with Multiple Rollback Segments. (Bug #26590)
InnoDB did not reset table
AUTO_INCREMENT values to the last used values
after a server restart.
A unique index on a column prefix could not be upgraded to a primary index even if there was no primary index already defined. (Bug #51378)
When using the
EXAMPLE storage engine, when
the engine had been built as a plugin (instead of built in), and
DTrace probes had been enabled during the build, loading the
storage engine library failed due to a missing object table