Re: BUG #5443: Undetected deadlock situation

On fre, 2010-04-30 at 03:51 +0000, Claudio wrote:
> The following bug has been logged online:
>
> Bug reference:      5443
> Logged by:          Claudio
> Email address:      claudio@livra.com
> PostgreSQL version: 8.3.7
> Operating system:   CentOS
> Description:        Undetected deadlock situation
> Details:
>
> During a massive update of a table A, a single-row update of table A in
> another session created an undetected deadlock situation, as evidenced by
> the following locks (taken from pg_locks):
>
>    locktype    | database | relation | page  | tuple | virtualxid |
> transactionid | classid | objid | objsubid | virtualtransaction |  pid  |
>    mode       | granted
>  transactionid |          |          |       |       |            |
> 39773877 |         |       |          | 63/15761           | 11157 |
> ShareLock        | f
>  transactionid |          |          |       |       |            |
> 39773877 |         |       |          | 4/10902            |  6421 |
> ExclusiveLock    | t
>

This is not a deadlock.  It's just two locks on the same table, one is
granted, and the other one is waiting.  There needs to be more
information to make sense of this (and maybe a bit more readable
formatting).