From: | "Adam Rich" <adam(dot)r(at)sbcglobal(dot)net> |
---|---|
To: | "'Richard Yen'" <dba(at)richyen(dot)com>, <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: trying to make sense of deadlocks |
Date: | 2009-02-10 04:32:59 |
Message-ID: | 0e8801c98b38$a7c64c70$f752e550$@r@sbcglobal.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> -----Original Message-----
> From: pgsql-general-owner(at)postgresql(dot)org [mailto:pgsql-general-
> owner(at)postgresql(dot)org] On Behalf Of Richard Yen
> Sent: Monday, February 09, 2009 4:18 PM
> To: pgsql-general(at)postgresql(dot)org
> Subject: [GENERAL] trying to make sense of deadlocks
>
> Hi,
>
> I'm trying to make sense of a situation I ran into this morning.
> Apparently, there were numerous deadlocks (approx. 75 in a 30-min
> period) while procs were trying to write to a table (16634, "account")
> in my database.
>
> Just to give you a sense of what's going on, process 22583 tried to do
> an insert, followed by an update, and the insert took 225925.724 ms:
>
>
> Might someone be able to help me make more sense of this?
>
The two processes that are conflicting, can you list everything they do
since the beginning of the transaction until the deadlock?
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-02-10 04:52:15 | Re: trying to make sense of deadlocks |
Previous Message | Scott Marlowe | 2009-02-10 02:36:28 | Re: Out of memory on SELECT in 8.3.5 |