| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | darcy(at)druid(dot)net (D'Arcy J(dot)M(dot) Cain) |
| Cc: | pgsql-hackers(at)PostgreSQL(dot)org |
| Subject: | Re: WaitOnLock |
| Date: | 2000-10-04 15:57:20 |
| Message-ID: | 3478.970675040@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
darcy(at)druid(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-10-04 16:08:27 | Re: I want tips for debugging deadlocks |
| Previous Message | Tom Lane | 2000-10-04 15:49:30 | Re: yacc guru needed |