From: | Claudio Freire <claudio(at)livra(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, 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:53:35 |
Message-ID: | 1272650015.4905.3.camel@klauss.livra.local |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Fri, 2010-04-30 at 12:32 -0400, Tom Lane wrote:
> "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
> > 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:
>
> An even better thing, if you can spare a few minutes for analysis
> next time it happens, is to attach to each backend process with gdb
> and get a stack trace. If there is a deadlock that would probably
> be enough information to understand what it is.
Interesting idea... I'll see if I have gdb (or can install it) on the
server.
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2010-04-30 17:57:36 | Re: plpython memory leak uppon empty resultsets in all versions |
Previous Message | Claudio Freire | 2010-04-30 17:52:52 | Re: BUG #5443: Undetected deadlock situation |