Re: deadlock of lock-waits (on transaction and on tuple) using same update statement

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Andrej Vanek <andrej(dot)vanek(dot)sk(at)gmail(dot)com>
Cc: Bill Moran <wmoran(at)potentialtech(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: deadlock of lock-waits (on transaction and on tuple) using same update statement
Date: 2014-09-25 14:05:02
Message-ID: 20140925140502.GX5311@eldon.alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Andrej Vanek wrote:
> Hi,
>
>
> now I've checked release-notes of 9.3.5 (my version 9.3.4)- found a fix
> which probably could lead to my deadlocks:
>
> > Fix race condition when updating a tuple concurrently locked by another
> > process (Andres Freund,Álvaro Herrera)
>
> How can I make sure I've run into this bug?

Update and see if you can reproduce the bug there. If you can, let us
know; I didn't trace through your example and won't unless you confirm
it's still an issue.

It's a bad idea to run any 9.3 version other than the latest one. There
are some ugly bugs in there.

--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Thomas Kellerer 2014-09-25 14:24:46 Re: Synchronous replication + pgPool: not all transactions immediately visible on standby
Previous Message Adrian Klaver 2014-09-25 13:58:00 Re: Installing Postgresql on Linux Friendlyarm