Sergei, please run CHECK TABLE on the tables, and check if it prints something to the .err log.
Also, resolve the stack trace printed by the crashing mysqld, as explained in the manual. Best regards, Heikki Tuuri Innobase Oy Foreign keys, transactions, and row level locking for MySQL InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up MyISAM tables http://www.innodb.com/order.php Order MySQL technical support from https://order.mysql.com/ ----- Original Message ----- From: ""Sergei Skarupo"" <[EMAIL PROTECTED]> Newsgroups: mailing.database.myodbc Sent: Thursday, July 15, 2004 1:50 AM Subject: Expensive InnoDB queries crash mysql daemon > ------_=_NextPart_001_01C469F5.1B46DF30 > Content-Type: text/plain; > charset="iso-8859-1" > Content-Transfer-Encoding: quoted-printable > > Hello All, > =20 > I hope someone can shed some light on this problem... > =20 > This concerns large InnoDB tables (having on the order of millions of = > rows). > =20 > When I run ALTER TABLE (for example, to change the default column value) = > or UPDATE or DELETE queries that affect many rows, mysqld-max crashes = > and apparently gets restarted by mysqld_safe. This also seems to hang = > the web server that runs on the same machine and maintains connections = > with the database. Of course, the query does not complete. > =20 > I'm using mysql version 4.0.16 on Red Hat 9 Linux, kernel 2.4.20. > =20 > Thanks in advance, > =20 > Sergei > > ------_=_NextPart_001_01C469F5.1B46DF30-- -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
