On Tuesday November 9 2004 10:36, Tom Lane wrote:
> "Ed L." <[EMAIL PROTECTED]> writes:
> > I know the original statement is printed right after this, but with
> > complex triggers doing lots of write queries, I'm finding it difficult
> > to identify which subsequent query in the trigger is really
"Ed L." <[EMAIL PROTECTED]> writes:
> I know the original statement is printed right after this, but with complex
> triggers doing lots of write queries, I'm finding it difficult to identify
> which subsequent query in the trigger is really the one immediately
> preceding the deadlock. It would
I'm wrestling with tracking down a deadlock. Here's a 7.4.6 deadlock
message:
ERROR: deadlock detected
DETAIL: Process 15655 waits for ShareLock on transaction 9381; blocked by
process 15600.
Process 15600 waits for ShareLock on transaction 9388; blocked by process
15655.
I know the origin
