From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
Cc: | claudio(at)livra(dot)com, "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 16:32:52 |
Message-ID: | 26588.1272645172@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
"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.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-04-30 16:51:21 | Re: [9.0beta5/cvs head] build failure due to unchecked results |
Previous Message | Kevin Grittner | 2010-04-30 16:14:44 | Re: BUG #5443: Undetected deadlock situation |