End of Product LifecycleActive development and support for MySQL Database Server versions 3.23, 4.0, and 4.1 has ended. For details, see http://www.mysql.com/about/legal/lifecycle/#calendar. Please consider upgrading to a recent version. Further updates to the content of this manual will be minimal. All formats of this manual will continue to be available until 31 Dec 2010.
Changed to use autoconf 2.52 (from autoconf 2.13)
Fixed bug in complicated join with
Added internal safety checks for
InnoDB variables were always shown in
SHOW VARIABLES as
OFF on high-byte-first systems (like
InnoDB SQL optimizer to favor
index searches more often over table scans.
Fixed a performance problem with
tables when several large
SELECT queries are run
concurrently on a multiprocessor Linux computer. Large
SELECT queries now
also generally run faster on all platforms.
If MySQL binary logging is used,
prints after crash recovery the latest MySQL binary log name
and the offset
InnoDB was able to recover
to. This is useful, for example, when resynchronizing a master
and a slave database in replication.
Added better error messages to help in installation problems
It is now possible to recover MySQL temporary tables that have
become orphaned inside the
InnoDB now prevents a
KEY declaration where the signedness is not the same
in the referencing and referenced integer columns.
If inserts to several tables containing an
AUTO_INCREMENT column were wrapped inside
InnoDB asserted in
In 3.23.47 we permitted several
UNIQUE secondary index for an
InnoDB table. But
CHECK TABLE was not relaxed: it
reports the table as corrupt.
TABLE no longer complains in this situation.