From: | "Michael P(dot) Soulier" <michael_soulier(at)mitel(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | apparent deadlock |
Date: | 2008-11-18 18:43:53 |
Message-ID: | 20081118184353.GA31334@e-smith.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hello,
I'm working with Pg 7.4 on CentOS, and I'm seeing an apparent deadlock which
is not resolving itself.
According to the postgres documentation, deadlocks should be detected and
resolved by killing one or more transactions involved.
http://www.postgresql.org/docs/current/static/explicit-locking.html
What I'm seeing is an upgrade of an application running a series of alter
table commands to migrate the db schema, but blocking during the process and
never continuing. I finally had to restart the db to unblock the process.
Does anyone have any suggestions for troubleshooting a potential deadlock like
this? I'm not sure how to query existing locks on tables, for example, which
might tell me where the issue is.
Thank you,
mps
--
Michael P. Soulier <michael_soulier(at)mitel(dot)com>, 613-592-2122 x2522
"Any intelligent fool can make things bigger and more complex... It takes a
touch of genius - and a lot of courage to move in the opposite direction."
--Albert Einstein
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-11-18 18:46:22 | Re: MVCC and index-only read |
Previous Message | Tom Lane | 2008-11-18 18:41:49 | Re: Slow queries when ORDER BY ... DESC with table inheritance (no index scan backwards) |