Tom Lane <[EMAIL PROTECTED]> writes: > Greg Stark <[EMAIL PROTECTED]> writes: > > > 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.
Oops, didn't see this before I sent my last message. Brendan, in case it's not clear, in case of a conflict between my explanation and Tom's listen to Tom. :) -- greg ---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend
