Hello.
If you have a reproducible test case, you should report a bug. Andreas Unterkircher <[EMAIL PROTECTED]> wrote: > I can now isolate the problems with the appearing "lock" of some queries. > > I updated MySQL from 4.1 to 5beta > (mysql-standard-5.0.10-beta-linux-x86_64-glibc23) to test if the problem > still appears > in the newer version. I made a full sqldump on the old server and import > it successfully on the new server. > > If I start MySQL5 manually (bin/mysqld_safe --user=mysql &) I have > absolutely no troubles. > > Then I addepted the debian mysql init start script to the needings of > the new MySQL5 installation. The Debian-Script makes a > mysqlcheck of every table after the MySQL-Server is up and running. > > After mysqlcheck finished (irrelevant if storage engine is MyISAM or > InnoDB) the "lock" problem comes back again. I guess > that the index of these tables getting corrupted some how. I can also > reproduce this with CHECK TABLE, ANALYZE TABLE, > REPAIR TABLE and OPTIMIZE TABLE. > > I can fix the problem, if I restart the server to get away these > unkillable queries and make a > ALTER TABLE tablename TYPE=innodb > or > ALTER TABLE tablename TYPE=myisam > - but this helps only till next time I run a table check or optimizer on > these tables.... > > Cheers, > Andreas > > > > > -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
