AND q.status = 'parse'
ORDER BY q.file_size ASC, q.created ASC, q.queue_id ASC
LIMIT 1
However, as I execute this query several times each minute from different
applications, I frequently get these messages:
DB ERROR: SQLSTATE[40001]: Serialization failure: 1213 Deadlock found when
trying to get lock
each minute from different
applications, I frequently get these messages:
DB ERROR: SQLSTATE[40001]: Serialization failure: 1213 Deadlock found when
trying to get lock; try restarting transaction
Am I writing my query wrong or expecting behavior that MySQL doesn't
support?
-- Dante
[40001]: Serialization failure: 1213 Deadlock found
when
trying to get lock; try restarting transaction
Am I writing my query wrong or expecting behavior that MySQL doesn't
support?
-- Dante
--
- michael dykman
- mdyk...@gmail.com
May the Source be with you.
--
MySQL
found when
trying to get lock; try restarting transaction
Am I writing my query wrong or expecting behavior that MySQL doesn't
support?
-- Dante
--
--
D. Dante Lorenso
da...@lorenso.com
972-333-4139
--
MySQL General Mailing List
For list
execute this query several times each minute from different
applications, I frequently get these messages:
DB ERROR: SQLSTATE[40001]: Serialization failure: 1213 Deadlock found when
trying to get lock; try restarting transaction
Am I writing my query wrong or expecting behavior that MySQL doesn't
: 1213 Deadlock found
when
trying to get lock; try restarting transaction
Am I writing my query wrong or expecting behavior that MySQL doesn't
support?
--
- michael dykman
- mdyk...@gmail.com
May the Source be with you.
--
MySQL General Mailing List
For list archives: http
= 'parse'
ORDER BY q.file_size ASC, q.created ASC, q.queue_id ASC
LIMIT 1
However, as I execute this query several times each minute from
different
applications, I frequently get these messages:
DB ERROR: SQLSTATE[40001]: Serialization failure: 1213 Deadlock
found
when
trying to get lock
/2010 03:43 PM
Subject:
Re: Serialization failure: 1213 Deadlock found when trying to get lock;
try restarting transaction
Try to run
SHOW ENGINE INNODB STATUS;
Near the top there will be some information on the latest deadlock.
That might help you to understand what is deadlocking. Sometimes