Re: Confusing deadlock report - Mailing list pgsql-general

From Albe Laurenz
Subject Re: Confusing deadlock report
Date
Msg-id A737B7A37273E048B164557ADEF4A58B53810A39@ntex2010i.host.magwien.gv.at
Whole thread Raw
In response to Re: Confusing deadlock report  (Thomas Kellerer <spam_eater@gmx.net>)
Responses Re: Confusing deadlock report  (Rakesh Kumar <rakeshkumar464a3@gmail.com>)
List pgsql-general
Thomas Kellerer wrote:
>> Can you determine what statements were executed in these transactions before the deadlock?
>> It was probably one of these that took the conflicting lock.
> 
> Unfortunately not. Statement logging is not enabled on that server (space-constrained).
> 
> And while we know the statements that can possibly be executed by these parts of the application,
> several on them depend on the actual data, so it's hard to tell which path the two transactions
> actually used.

But that's where the solution to your problem must be...

Look at all statements that modify "alpha" and could be in the same transaction
with the INSERT to "bravo".

Yours,
Laurenz Albe

pgsql-general by date:

Previous
From: Dang Minh Huong
Date:
Subject: log temp files are created twice in PL/pgSQL function
Next
From: Pavel Stehule
Date:
Subject: Re: log temp files are created twice in PL/pgSQL function