| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Brian Cox <bcox(at)wilytech(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: insert deadlock |
| Date: | 2005-12-06 21:16:11 |
| Message-ID: | 16396.1133903771@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Brian Cox <bcox(at)wilytech(dot)com> writes:
> There are no foreign key constraints from/to A or B to/from C.
How sure are you of that? FK conflicts are much the most common reason
for unexpected deadlocks in pre-8.1 PG releases.
> 2005-12-02 15:04:46,773 [TP-Processor8] INFO
> [com.timestock.tess.services.processors.DefectProcessor] - <SQLException>
> java.sql.SQLException: ERROR: deadlock detected
Java is doing you no favors here by suppressing the detail message that
would have told you exactly who blocked on what. Perhaps you can get
the detail by looking in the postmaster log, though.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2005-12-06 21:24:34 | Re: insert deadlock |
| Previous Message | W. Haslbeck | 2005-12-06 21:04:34 | Winbashing |