Rachit Siamwalla <[EMAIL PROTECTED]> writes:
> Anyone know why I could possibly get this error? This doesn't happen
> deterministically.
It wouldn't, because the problem arises from the interaction of multiple
clients --- AFAIK it is not possible to get that error with only a
single client, no ma
Anyone know why I could possibly get this error? This doesn't happen
deterministically.
WaitOnLock: error on wakeup - Aborting this transaction
I also got this notice:
NOTICE: Deadlock detected -- See the lock(l) manual page
---
Actually, what I'm looking for in this mail is a possible way
[EMAIL PROTECTED] (D'Arcy J.M. Cain) writes:
> WaitOnLock: error on wakeup - Aborting this transaction
What happens to NOTICEs in your application?
For some odd reason, deadlock reports come out as a NOTICE followed by
this error message; if you are bit-bucketing NOTICEs then you may well
be con
A client just got this error. Anyone know why I suddenly get this?
The program has been working flawlessly for months before this.
WaitOnLock: error on wakeup - Aborting this transaction
--
D'Arcy J.M. Cain| Democracy is three wolves
http://www.druid.net/darcy/| and a she
