On May 13, 2008, at 5:00 PM, Tom Lane wrote:
Tino Schwarze <postgresql@xxxxxxx> writes:
On Tue, May 13, 2008 at 01:18:24PM -0600, kevin kempter wrote:
ProgrammingError: deadlock detected
DETAIL: Process 23098 waits for ShareUpdateExclusiveLock on
relation 428126 of database 427376; blocked by process 23916.
Process 23916 waits for ShareLock on transaction 46802680; blocked
by process 23098.
I've never figured out how to resolve the "lock on transaction" to
something understandable...
It's presumably waiting for a row lock that the other transaction
has got. We don't keep enough information about row locks in memory
to give a better error message (because we could run out of memory
if we tried :-()
regards, tom lane
If that's true does it make sense to play with a timeout value (I
assume the timeout is configurable somewhere in postgresql.conf) in an
effort to tune for this ?
/Kevin
--
Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
