Re: BUG #5443: Undetected deadlock situation

From: Claudio Freire <claudio(at)livra(dot)com>
To: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5443: Undetected deadlock situation
Date: 2010-04-30 17:52:52
Message-ID: 1272649972.4905.1.camel@klauss.livra.local
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, 2010-04-30 at 11:14 -0500, Kevin Grittner wrote:

> Claudio Freire <claudio(at)livra(dot)com> wrote:
>
> > I know it doesn't look like a deadlock from where you're standing,
> > but it does so from where I am.
>
> It's possible that you're filtering out the information which would
> be most useful to diagnosing the problem. Next time it happens,
> please send the entire output from pg_locks and pg_stat_activity
> (preferably as attachments to avoid wrapping issues), along with the
> information listed under "Things you need to mention" on this page:

pg_stat_activity not, but pg_locks I did save:

Attachment Content-Type Size
locks.txt text/plain 4.8 KB

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Claudio Freire 2010-04-30 17:53:35 Re: BUG #5443: Undetected deadlock situation
Previous Message Tom Lane 2010-04-30 17:39:32 Re: plpython memory leak uppon empty resultsets in all versions