在 Feb 9, 2009 8:52 PM 時， Tom Lane 寫到：
Richard Yen writes:
It seems like all the deadlocks are for tuple (3,60), but strangely,
tuple (3,60) on the account table doesn't exist. Perhaps it was
deleted? According to the account table, the account with id = 39271
(which the UPDATE statements ca
Richard Yen writes:
> It seems like all the deadlocks are for tuple (3,60), but strangely,
> tuple (3,60) on the account table doesn't exist. Perhaps it was
> deleted? According to the account table, the account with id = 39271
> (which the UPDATE statements call for) corresponds to tuple
> -Original Message-
> From: pgsql-general-ow...@postgresql.org [mailto:pgsql-general-
> ow...@postgresql.org] On Behalf Of Richard Yen
> Sent: Monday, February 09, 2009 4:18 PM
> To: pgsql-general@postgresql.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 t
