Greg Stark <gsstark(at)mit(dot)edu> writes:
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
>> And what PG version is this? Alvaro fixed the
>> foreign-keys-take-exclusive-locks problem in 8.1 ...
> Except I don't think this is taking an exclusive lock at all. The original
> post had the deadlock detection fire on a SharedLock.
Yeah, but it was a ShareLock on a transaction ID, which is the trace
of something doing XactLockTableWait, which is only done if we're
blocking on a locked or updated-but-uncommitted row.
Since Brendan says he's using 8.1, the FK theory is out, and I think
what this probably is is a garden-variety deadlock on tuple updates, ie,
two concurrent transactions tried to update the same tuples in different
regards, tom lane
In response to
pgsql-performance by date
|Next:||From: Erwin Brandstetter||Date: 2006-05-28 21:56:27|
|Subject: Re: Query performance|
|Previous:||From: Brendan Duddridge||Date: 2006-05-28 19:17:07|
|Subject: Re: App very unresponsive while performing simple update |