| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Ben <bench(at)silentmedia(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Tracking down deadlocks |
| Date: | 2004-06-16 16:03:39 |
| Message-ID: | 22762.1087401819@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Ben <bench(at)silentmedia(dot)com> writes:
> I'm doing a bunch of data mining against a postgres database and have
> run into an interesting problem with deadlocks. The problem is,
> postgres is detecting them and then wacking the offending process, and
> I can't figure out what's causing them.
The processes involved in the deadlock should be identified in the
DETAIL message for the deadlock error. Perhaps you are using client
code that doesn't show you the DETAIL? If so, look in the postmaster
log. You can correlate the process PIDs mentioned in the message to
pg_stat_activity.procpid.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Fitzpatrick | 2004-06-16 16:14:29 | Remembering values in pl/pgsql |
| Previous Message | Csaba Nagy | 2004-06-16 15:54:06 | Re: Tracking down deadlocks |