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

From: Andrej Vanek <andrej(dot)vanek(dot)sk(at)gmail(dot)com>
To: Bill Moran <wmoran(at)potentialtech(dot)com>
Cc: 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 09:07:16
Message-ID: CAFNFRyH_vk_UhDduS4Dqd-yFEQ-ocHFhUxYL1uWYsUaeu-ncZg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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?

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Emanuel Araújo 2014-09-25 10:24:12 Re: How to clone CURRENT_DATE to SYSDATE ?
Previous Message Andrej Vanek 2014-09-25 07:49:46 Re: deadlock of lock-waits (on transaction and on tuple) using same update statement