Re: Proposal: new ereport option "errdetail_log"

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: "Decibel!" <decibel(at)decibel(dot)org>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Gregory Stark <stark(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Proposal: new ereport option "errdetail_log"
Date: 2008-04-02 23:55:23
Message-ID: 200804022355.m32NtN821407@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Decibel! wrote:
> > I don't have any immediate ideas for improvement either, but we
> > certainly shouldn't consider this a totally solved problem.
>
> Something I always find myself wanting when debugging locking issues
> is what's in pg_locks. Could we save that information somewhere when
> we detect a deadlock? In a real table would be nice, but I'd settle
> for just dumping it to a file somewhere. Or maybe into the logs.

That option will be in 8.4, logging deadlock information.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2008-04-03 00:15:49 Re: modules
Previous Message Ron Mayer 2008-04-02 23:41:16 modules