MySQL Forums
Forum List  »  InnoDB

Advanced Search
New Topic

Re: deadlock issue. Why is transaction waiting for an S lock when it already has an X lock?
Posted by: Richard Cook
Date: January 03, 2005 10:32PM

I just reread my post, and have a lot of typos. I apologize. Please let me clarify.

Also, I'm using version 4.0.22. The log is from a redhat box...

I'm seeing a deadlock which is confusing when I look at the log. It says here that Transaction 2 is waiting for a shared lock on the primary index of a table, one that it already has an X lock on.

Why is it waiting for an S lock, when it already has an X lock? Does it not realize this, or am I interpreting this incorrectly?

I'm looking through the source code, and see a function call lock_mode_stronger_or_eq() which I think would be used for this scenario, but I still haven't traced my way through the code...

Thanks for any help,
Rich

Navigate: Previous Message• Next Message
Options: Reply• Quote


Subject
Views
Written By
Posted
deadlock issue. Why is transaction waiting for an S lock when it already has an X lock?
3341
Richard Cook
January 03, 2005 05:49PM
Re: deadlock issue. Why is transaction waiting for an S lock when it already has an X lock?
2423
Richard Cook
January 03, 2005 10:32PM
Re: deadlock issue. Why is transaction waiting for an S lock when it already has an X lock?
2414
Heikki Tuuri
January 10, 2005 05:00PM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.