Re: BUG #13598: Hang forever, but must rollback (deadlock) - Mailing list pgsql-bugs

From Andres Freund
Subject Re: BUG #13598: Hang forever, but must rollback (deadlock)
Date
Msg-id 20150831133921.GB11441@awork2.anarazel.de
Whole thread Raw
In response to BUG #13598: Hang forever, but must rollback (deadlock)  (immortaldragonm@gmail.com)
Responses Re: BUG #13598: Hang forever, but must rollback (deadlock)  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-bugs
On 2015-08-31 08:03:51 +0000, immortaldragonm@gmail.com wrote:
> I think, that postgres must detect deadlock and rollback one of transaction
> with error. But it hang forever. Why? i think it's bug.

It's not a deadlock postgres can handle - the blocking part is in your
application. If these were submitted by two independent clients it'd
work.

Greetings,

Andres Freund

pgsql-bugs by date:

Previous
From: immortaldragonm@gmail.com
Date:
Subject: BUG #13598: Hang forever, but must rollback (deadlock)
Next
From: "David G. Johnston"
Date:
Subject: Re: BUG #13598: Hang forever, but must rollback (deadlock)