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 the one > > immediately preceding the deadlock. It would be helpful in debugging > > if the error message included info on which tables are involved, maybe > > even the deadlocking query itself, in the "DETAIL" output for future > > releases. > > I suppose the problem here has to do with conflicting SELECT FOR UPDATEs > from foreign-key references.
That appears to be the issue. We upgraded to 7.4.6 (thanks to slony, production downtime was minimal), then used 7.4.6 debug output to track relations, then guessed on fkey references, dropped them, and viola, no more deadlock. Thanks, Ed ---------------------------(end of broadcast)--------------------------- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
