CRITICAL bug in 4.1.2 if one specifies innodb_file_per_table in Unix!

Hi!

MySQL/InnoDB-4.1.2 is totally broken and useless if one has specified
innodb_file_per_table in my.cnf on Unix!

In crash recovery, InnoDB scans the database directories under the datadir,
and opens files in in the read-only mode. But the exclusive file lock that
InnoDB uses on the files fails in this case! The result is that the crash
recovery is NOT applied to those tables, and the tables become corrupt and
inaccessible!

My apologies for users, the fact that this bug got into 4.1 was due to
improper testing.

Heikki
Innobase Oy


--
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

Re: CRITICAL bug in 4.1.2 if one specifies innodb_file_per_table in Unix!

------_=_NextPart_001_01C44E5D.1B8395F0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Heikki,

=20

We are developing a quite big system, so we were planning to =
use innodb_per_table_tablespaces in our mysql database.

=20

Do we have any stable mysql version with innodb engine which =
supports the "per_table" feature ?

We are using RedHat Advanced Server based on Intel platform.

=20

Thanks in advance!!!

=20

Ing. Laura S. Rado

Especialista T=E9cnico

Base de Datos

TopGroup S.A.

=20

http://www.topgroup.com.ar =20

Bme. Mitre 739 - 6=BA Piso

(C1036AAM) Bs. As. Argentina

Tel.: +54 (11) 5238-0505 (Int. 112)

Fax: +54 (11) 5238-0506

lrado@topgroup.com.ar

=20

=20


------_=_NextPart_001_01C44E5D.1B8395F0--