Re: BUG #13598: Hang forever, but must rollback (deadlock)

From: Andres Freund <andres(at)anarazel(dot)de>
To: immortaldragonm(at)gmail(dot)com
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #13598: Hang forever, but must rollback (deadlock)
Date: 2015-08-31 13:39:21
Message-ID: 20150831133921.GB11441@awork2.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 2015-08-31 08:03:51 +0000, immortaldragonm(at)gmail(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message David G. Johnston 2015-08-31 13:57:46 Re: BUG #13598: Hang forever, but must rollback (deadlock)
Previous Message immortaldragonm 2015-08-31 08:03:51 BUG #13598: Hang forever, but must rollback (deadlock)