Deadlock on the same select for update

From: Roman <roman(dot)janowczyk(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Deadlock on the same select for update
Date: 2011-02-21 13:16:48
Message-ID: 4c6099f0-24e1-4d93-aaae-80b09596706b@4g2000yqo.googlegroups.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi,
I have problem with deadlocks and don't know why it happens. Below is
the log (postgres 9.0, debian):

[11882]DETAIL: Process 11882 waits for ShareLock on transaction
44324308; blocked by process 11884.
Process 11884 waits for ShareLock on transaction 44324307;
blocked by process 11882.

Process 11882: SELECT * FROM teddy WHERE id IN
(112747007,112747008,112747011,112747013,112747015,112747016,112747020,112747021,112747022,112747024,112747025,112747028,112747030,112747032,112747034,112747035,112747038,112747043,112747044,112747045,112747050,112747052,112747053)
FOR UPDATE

Process 11884: SELECT * FROM teddy WHERE id IN
(112747007,112747008,112747011,112747013,112747015,112747016,112747020,112747021,112747022,112747024,112747025,112747028,112747030,112747032,112747034,112747035,112747038,112747043,112747044,112747045,112747050,112747052,112747053)
FOR UPDATE

Regards,
Roman

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Geoffrey Myers 2011-02-21 13:24:44 Re: disable triggers using psql
Previous Message Andrew Sullivan 2011-02-21 12:51:35 Re: Worst case scenario of a compromised non super-user PostgreSQL user account