MySQL/InnoDB-4.0.24 is released

Hi!

InnoDB is the MySQL table type that supports FOREIGN KEY constraints,
transactions, row-level locking that is never escalated, multiversioned
concurrency control, asynchronous unbuffered disk I/O on Windows, and a
non-free online hot backup tool. InnoDB is an 'ACID'-compliant table type.

InnoDB is included in all MySQL downloads from http://www.mysql.com, and in
the commercial MySQL Pro license.

Release 4.0.24 is a bugfix release of the old stable MySQL-4.0 branch.

Please observe this bug fix in upcoming 4.0.25:

* Fixed a bug: MySQL-4.0.23 and 4.0.24 could complain that an InnoDB table
created with MySQL-3.23.49 or earlier was in the new compact InnoDB table
format of 5.0.3 or later, and InnoDB would refuse to use that table. (The
same bug exists in 4.1.8 - 4.1.10.) There is nothing wrong with the table,
it is mysqld that is in error. Workaround: wait that 4.0.25 or 4.1.11 is
released before doing an upgrade, or dump the table and recreate it with any
MySQL version >= 3.23.50 before upgrading to 4.0.23 or 4.0.24.


Full changelog for 4.0.24:

Functionality changed or added:

* Added configuration option and settable global variable
innodb_autoextend_increment for setting the size in megabytes by which
InnoDB tablespaces are extended when they become full. The default value is
8, corresponding to the fixed increment of 8 MB in previous versions of
MySQL.

* Do not acquire an internal InnoDB table lock in LOCK TABLES if
AUTOCOMMIT=1. This helps in porting old MyISAM applications to InnoDB.
InnoDB table locks in that case caused deadlocks very easily.

Bugs fixed:

* Work around a problem in AIX 5.1 patched with ML7 security patch: InnoDB
would refuse to open its ibdata files, complaining about an operating system
error 0.

* Fixed a memory corruption bug if one created a table with a primary key
that contained at least two column prefixes. An example: CREATE TABLE t(a
char(100), b tinyblob, PRIMARY KEY(a(5), b(10))).

* Use native tmpfile() function on Netware. All InnoDB temporary files are
created under sys:\tmp. Previously, InnoDB temporary files were never
deleted on Netware.

* Honor the --tmpdir startup option when creating temporary files.
Previously, InnoDB temporary files were always created in the temporary
directory of the operating system. On Netware, InnoDB will continue to
ignore --tmpdir. (Bug #5822)

* Fix a theoretical hang over the adaptive hash latch in InnoDB if one runs
INSERT ... SELECT ... (binlog not enabled), or a multi-table UPDATE or
DELETE, and only the read tables are InnoDB type, the rest are MyISAM; this
also fixes bug #7879 for InnoDB type tables. (Bug #7879)

* Fixed a bug: 32-bit mysqld binaries built on HP-UX-11 did not work with
InnoDB files greater than 2 GB in size. (Bug #6189)

* Fixed a bug: InnoDB failed to drop a table in the background drop queue if
the table was referenced by a foreign key constraint.

* Fixed a bug: if we dropped a table where an INSERT was waiting for a lock
to check a FOREIGN KEY constraint, then an assertion would fail in
lock_reset_all_on_table(), since that operation assumes no waiting locks on
the table or its records.

Best regards,

Heikki Tuuri
Innobase Oy
http://www.innodb.com


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=gcdmg-mysql@m.gmane.org