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

From Andrej Vanek
Subject Re: deadlock of lock-waits (on transaction and on tuple) using same update statement
Date
Msg-id CAFNFRyH_vk_UhDduS4Dqd-yFEQ-ocHFhUxYL1uWYsUaeu-ncZg@mail.gmail.com
Whole thread Raw
In response to Re: deadlock of lock-waits (on transaction and on tuple) using same update statement  (Andrej Vanek <andrej.vanek.sk@gmail.com>)
Responses Re: deadlock of lock-waits (on transaction and on tuple) using same update statement  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List 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?

pgsql-general by date:

Previous
From: Andrej Vanek
Date:
Subject: Re: deadlock of lock-waits (on transaction and on tuple) using same update statement
Next
From: Emanuel Araújo
Date:
Subject: Re: How to clone CURRENT_DATE to SYSDATE ?