Re: BUG #5443: Undetected deadlock situation

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Peter Eisentraut" <peter_e(at)gmx(dot)net>,"Claudio" <claudio(at)livra(dot)com>
Cc: <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #5443: Undetected deadlock situation
Date: 2010-04-30 13:47:50
Message-ID: 4BDA993702000025000310CD@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:

> This is not a deadlock.

Agreed.

> It's just two locks on the same table

Not as I read it.

> (and maybe a bit more readable formatting).

Eliminating null columns and mangling column headers for length, I
get this:

>> locktype | tranid | virtualx | pid | mode | gr
>> transactionid | 39773877 | 63/15761 | 11157 | ShareLock | f
>> transactionid | 39773877 | 4/10902 | 6421 | ExclusiveLock | t

So it looks like two locks on the same transaction ID by different
transactions. How does that happen?

-Kevin

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Claudio Freire 2010-04-30 14:01:11 Re: BUG #5443: Undetected deadlock situation
Previous Message Peter Eisentraut 2010-04-30 13:16:52 Re: BUG #5443: Undetected deadlock situation