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: Heikki Tuuri
Date: January 10, 2005 05:00PM

Richard,

Trx 2 is waiting for an S lock on the record AND the gap before the record.

Trx 2 already has the X lock only on the record.

We will look into optimizing this case in lock0lock.c in 4.1.xx. I guess InnoDB could grant the lock to Trx 2, because Trx 2 is only missing the gap part of the lock.

Best regards,

Heikki
Oracle Corp./Innobase Oy
InnoDB - transactions, row level locking, and foreign keys for MySQL

InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up MyISAM tables
http://www.innodb.com/order.php

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?
3891
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?
2738
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?
2713
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.