: innodb deadlock leads to server crash
From: Heikki Tuuri
Date: Mon, 3 Mar 2003 10:42:48 +0200
Hi!
Ok, now I think I understand the problem. Since you use the -q option, the
client mysql retrieves rows in the result set in chunks of some size. As
InnoDB keeps the adaptive hash index latch S
InnoDB.
Thank you,
Heikki
- Original Message -
From: "Heikki Tuuri" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, March 03, 2003 10:24 AM
Subject: Re: innodb deadlock leads to server crash
> Hi!
>
> Your email address gives the error:
>
>
MAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Monday, March 03, 2003 10:05 AM
Subject: Re: innodb deadlock leads to server crash
> Hi!
>
> A deadlock of threads is a bug. It is is not connected to transactions or
> multiversioning.
>
> Is the problem repeatable in your comp
the online manual and latest news on InnoDB
sql query
- Original Message -
From: <[EMAIL PROTECTED]>
Newsgroups: mailing.database.mysql
Sent: Monday, March 03, 2003 3:58 AM
Subject: innodb deadlock leads to server crash
> >Description:
> A deadlock within innodb leads to
>Description:
A deadlock within innodb leads to a server crash.
I have a large table which I need to update in-place. So one mysql
connection does a SELECT, and another updates the data. I thought
that, since innodb supports transactions and multiversioning, the
