Re: Random Deadlock on DROP CONSTRAINT

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: Mark Mandel <mark(dot)mandel(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Random Deadlock on DROP CONSTRAINT
Date: 2009-03-08 21:29:17
Message-ID: dcc563d10903081429p6119556cif6b06411eea6db6b@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Sun, Mar 8, 2009 at 2:54 PM, Mark Mandel <mark(dot)mandel(at)gmail(dot)com> wrote:
> Just a note on this -
>
> I have tried it on both 8.2 and 8.3
>
> Maybe 'deadlock' isn't the right word, so much as 'hang'.. in that
> once it decided to stop at that point, it goes no further, unless I
> restart the app server that has the connecton to the database.
>
> It seems to be completely random, and I'm got no idea what is going on.

Well, pg_locks can tell you, and us, a lot. Next time it's happening
grab the contents of pg_locks and attach it to an email here. Most
likely it's some long running transaction or something blocking the
access you need.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Mark Mandel 2009-03-08 22:52:21 Re: Random Deadlock on DROP CONSTRAINT
Previous Message Scott Marlowe 2009-03-08 21:27:35 Re: [Q] Cluster design for geographically separated dbs