MySQL/InnoDB-4.1.11 is released

Hi!

MySQL/InnoDB-4.1.11 is a bugfix release of the stable 4.1 branch. This
branch is recommended for production use. There are no important bug fixes
in 4.1.11, for most users there is no need to upgrade from 4.1.10.

InnoDB is the MySQL table type that supports foreign key constraints,
transactions, row-level locking, non-locking consistent read (MVCC), all
four SQL-1992 isolation levels of transactions, multiple tablespaces,
asynchronous unbuffered disk I/O on Windows, and a non-free hot online
backup tool.


Functionality added or changed:

* When MySQL/InnoDB is compiled on Mac OS X 10.2 or earlier, detect the
operating system version at run time and use the fcntl() file flush method
on Mac OS X versions 10.3 and later. Apple had disabled fsync() in Mac OS X
for internal disk drives, which caused corruption at power outages.

* A shared record lock (LOCK_REC_NOT_GAP) is now taken for a matching record
in the foreign key check because inserts can be allowed into gaps.

* Relaxed locking in INSERT...SELECT, single table UPDATE...SELECT and
single table DELETE...SELECT clauses when innobase_locks_unsafe_for_binlog
is used and isolation level of the transaction is not serializable. InnoDB
uses consistent read in these cases for a selected table.


Bugs fixed:

* Fixed a bug introduced in 4.1.9 to the Windows version if you used
innodb_file_per_table. mysqld would stop and complain about Windows error
number 87 in a file operation. (See the Bugs database or the 4.1.9 change
notes about a workaround for that bug in 4.1.9). (Bug #8021)

* Corrected the handling of trailing spaces in the ucs2 character set. (Bug
#7350)

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

* Fix a race condition that could cause the assertion
space->n_pending_flushes == 0 to fail in fil0fil.c, in fil_space_free(), in
DROP TABLE or in ALTER TABLE.

* ALTER TABLE ... ADD CONSTRAINT PRIMARY KEY ... complained about bad
foreign key definition. (Bug #7831)

* 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. (Bug
#7879)

* If MySQL wrote to its binlog, but for some reason, trx->update_undo and
@code{trx->insert_undo} were NULL in InnoDB, then trx->commit_lsn was
garbage, and InnoDB could assert in the log flush of
trx_commit_complete_for_mysql(). (Bug #9277)

* If InnoDB cannot allocate memory, keep retrying for 60 seconds before we
intentionally crash mysqld; maybe the memory shortage is just temporary.

* If one used LOCK TABLES, created an InnoDB temp table, and did a
multi-table update where a MyISAM table was the update table and the temp
table was a read table, then InnoDB asserted in row0sel.c because
n_mysql_tables_in_use was 0. Also, we remove the assertion altogether and
just print an error to the .err log if this important consistency check
fails. (Bug #8677)

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