From: | Alfranio Correia Junior <alfranio(at)lsd(dot)di(dot)uminho(dot)pt> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | strange behavior on locks |
Date: | 2006-01-21 01:54:44 |
Message-ID: | 1137808484.29814.18.camel@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
I running PostgreSQL 8.0.x with database that does not have foreign keys
and sometimes the following messages appears:
ERROR: deadlock detected
DETAIL: Process 10029 waits for ShareLock on transaction 65272; blocked
by process 32436.
Process 32436 waits for ShareLock on transaction 65117; blocked
by process 10029.
I also see (right after executing a ps) that there are lots of messages
"select waiting".
1 - Does it mean that process 10029 owns transaction 65117 and
process 32436 owns transaction 65272 as a transaction acquires an
exclusive lock in its transaction id ?
2 - How is this situation possible ?
What could cause the status ("select waiting") ?
Best regards,
Alfranio
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2006-01-21 02:18:14 | Re: [HACKERS] Inconsistent syntax in GRANT |
Previous Message | Tom Lane | 2006-01-21 01:25:35 | Re: panic on 7.3 |