# [EMAIL PROTECTED] / 2003-06-04 17:11:19 +0300:
> Roman,
>
> looks like your application fails to commit this transaction:
>
> "
> 030604 13:52:21 INNODB MONITOR OUTPUT
> ...
> LIST OF TRANSACTIONS FOR EACH SESSION:
> ---TRANSACTION 0 407759, ACTIVE 2090 sec, OS thread id 10251
> 10 lock struct(s), heap size 1024, undo log entries 5
> MySQL thread id 1, query id 914 localhost www
> ...
> "
>
> Why is it lingering idle for over 30 minutes?
No idea, will investigate and report back. Thanks for the pointer,
that was the poke I was looking for! :)
> "
> TABLE LOCK table webed/section_txt trx id 0 407759 lock_mode IX
> "
> InnoDB table locks are 'intention locks' which just mark that the
> transaction has some row locks in the table. Currently, the only use of for
> them is in the query cache of MySQL-4.1.
Thanks for this explanation.
--
If you cc me or remove the list(s) completely I'll most likely ignore
your message. see http://www.eyrie.org./~eagle/faqs/questions.html
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
