| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Gregory Stark <stark(at)enterprisedb(dot)com> |
| Cc: | Bill Moran <wmoran(at)potentialtech(dot)com>, tom(at)tacocat(dot)net, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: DeadLocks..., DeadLocks... |
| Date: | 2007-06-14 17:17:51 |
| Message-ID: | 20070614171751.GF27600@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Gregory Stark wrote:
>
> I'm still not precisely clear what's going on, it might help if you posted the
> actual schema and the deadlock message which lists the precise locks that
> deadlocked.
>
> Are any of the DML you mention on other tables on those tables with foreign
> key references to this one?
Maybe this has to do with FKs and an old release, which used SELECT FOR
UPDATE in the FK triggers. Those were well-known for causing deadlocks
back then.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rikard Pavelic | 2007-06-14 17:33:00 | Re: explain analyze on a function |
| Previous Message | Alvaro Herrera | 2007-06-14 17:16:58 | Re: explain analyze on a function |