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 07:49:46
Message-ID: CAFNFRyF-URJAwbJCdHM6oOBvuHOxYkRWKBpfikF8Y7M9QBwWPQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi Bill,

thanks for your answer.

> most often caused by something earlier in the transactions
> need all of the statements in each transaction

It would be great if we could reveal an application error.

Whole transactions I've already posted (in postgres log:
log_min_duration_statement=0).
Nothing suspicious yet:
- both sessions COMMIT/ROLLBACK before BEGIN
- both sessions run the same SQL statements
- deadlock: FIRST statement of both transactions
- deadlock: update single table, same row, column without any constraints
(WHY?)
- no statements of other sessions executed in between

Any idea?

thanks, Andrej

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Andrej Vanek 2014-09-25 09:07:16 Re: deadlock of lock-waits (on transaction and on tuple) using same update statement
Previous Message Xiang Gan 2014-09-25 06:34:33 Re: Installing Postgresql on Linux Friendlyarm