I noticed this deadlock in show innodb status on a mysql 4.0.14 box
today. Both transactions seem to be trying to execute the a query on
the same record, which I don't think should cause a deadlock. What am I
missing?
030911 10:12:45
*** (1) TRANSACTION:
TRANSACTION 0 153127600, ACTIVE 53 sec, p
t; <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Friday, September 12, 2003 1:53 AM
Subject: innodb deadlock issue
> I noticed this deadlock in show innodb status on a mysql 4.0.14 box
> today. Both transactions seem to be trying to execute the a query on
> the s
nal Message -
> From: "Joe Shear" <[EMAIL PROTECTED]>
> Newsgroups: mailing.database.myodbc
> Sent: Friday, September 12, 2003 1:53 AM
> Subject: innodb deadlock issue
>
>
> > I noticed this deadlock in show innodb status on a mysql 4.0.14 box
> > t
;
Cc: <[EMAIL PROTECTED]>
Sent: Friday, September 12, 2003 2:43 AM
Subject: Re: innodb deadlock issue
> user_id is the primary key..
>
> relevant parts of show create table:
> | plx_user |CREATE TABLE `plx_user` (
> `user_id` int(11) NOT NULL auto_increment,
> `is_delete
