Search Postgresql Archives

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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: deadlock of lock-waits (on transaction and on tuple) using same update statement
From: Andrej Vanek <andrej.vanek.sk@xxxxxxxxx>
Date: Thu, 25 Sep 2014 11:07:16 +0200
Cc: pgsql-general <pgsql-general@xxxxxxxxxxxxxx>
In-reply-to: <CAFNFRyF-URJAwbJCdHM6oOBvuHOxYkRWKBpfikF8Y7M9QBwWPQ@mail.gmail.com>

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?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Follow-Ups:
- Re: deadlock of lock-waits (on transaction and on tuple) using same update statement
  - From: Alvaro Herrera

References:
- deadlock of lock-waits (on transaction and on tuple) using same update statement
  - From: Andrej Vanek
- Re: deadlock of lock-waits (on transaction and on tuple) using same update statement
  - From: Bill Moran
- Re: deadlock of lock-waits (on transaction and on tuple) using same update statement
  - From: Andrej Vanek

Prev by Date: Re: deadlock of lock-waits (on transaction and on tuple) using same update statement
Next by Date: Re: How to clone CURRENT_DATE to SYSDATE ?
Previous by thread: Re: deadlock of lock-waits (on transaction and on tuple) using same update statement
Next by thread: Re: deadlock of lock-waits (on transaction and on tuple) using same update statement
Index(es):
- Date
- Thread

[Index of Archives] [Postgresql Jobs] [Postgresql Admin] [Postgresql Performance] [Linux Clusters] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Books] [PHP Databases] [Postgresql & PHP] [Yosemite]

Powered by Linux