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 <darcy@{druid|vex}.net>   |  Democracy is three wolves
http://www.druid.net/darcy/                |  and a sheep voting on
+1 416 425 1212     (DoD#0082)    (eNTP)   |  what's for dinner.

Wed, 4 Oct 2000 11:42:04 -0400 (EDT)
darcy@druid.net (D'Arcy J.M. Cain)
WaitOnLock
darcy@druid.net (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 confused.


Window 1:

regression=# begin;
BEGIN
regression=# lock int4_tbl;
LOCK TABLE

Window 2:

regression=# begin;
BEGIN
regression=# lock int8_tbl;
LOCK TABLE
regression=# lock int4_tbl;
<< waits >>

Window 1:

regression=# lock int8_tbl;
NOTICE:  Deadlock detected -- See the lock(l) manual page for a possible cause.
ERROR:  WaitOnLock: error on wakeup - Aborting this transaction


			regards, tom lane

Wed, 04 Oct 2000 11:57:20 -0400
Tom Lane <tgl@sss.pgh.pa.us>
Re: WaitOnLock 