Processing' ORDER BY t0.CREATION DATE ASC
14:47:09 22 Query commit
23 Quit
14:47:28 3 Query DROP TABLE innodb lock monitor
---End Query Log
- Original Message -
From: ""Heikki Tuuri"" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.mys
Wouter,
the Lock Monitor output tells that trx 370099 has been committed or rolled
back by the user. That is why the locks have disappeared.
Have you taken into account the following:
8.5 When does MySQL implicitly commit or rollback a transaction?
a.. MySQL has the autocommit mode switched on
Heikki,
Yep. That's why I use seperate connections for holding the lock and
to do the subsequent locking attempts. Besides, if that were the
problem, I would see the lock disappear at the very first failed
locking attempt, but that's not the case.
I thought it might be a connection timeout, but
Wouter,
- Original Message -
From: "Wouter Zelle" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.mysql
Sent: Wednesday, September 04, 2002 10:59 AM
Subject: Re: InnoDB locks disappear
> Heikki,
>
> Unfortunately it is not that easy. I've set the
&
Heikki,
Unfortunately it is not that easy. I've set the
innodb_lock_wait_timeout to 1 because I want locks to fail quickly,
so my program can move on to the next request. In pseudocode:
Fetch a bunch of requests with status=unprocessed
Try to obtain a lock through a select * from x for update
If
Wouter,
- Original Message -
From: "Wouter Zelle" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.mysql
Sent: Tuesday, September 03, 2002 7:43 PM
Subject: InnoDB locks disappear
> My program uses locks to allow for multi-threading (processing
> requests that are
My program uses locks to allow for multi-threading (processing
requests that are stored in the database using more than one thread
and/or application). The problem is that the locks disappear for
seemingly no reason at all. The same queries are repeated over and
over again until the lock just vani
