Re: Proposal: new ereport option "errdetail_log"

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Gregory Stark <stark(at)enterprisedb(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Proposal: new ereport option "errdetail_log"
Date: 2008-03-24 23:16:05
Message-ID: 20080324231605.GN5484@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Gregory Stark wrote:

> The axis on which I still see real room for improvement here is on the
> description of the locks. It's awfully hard for a user to tell from the
> deadlock message exactly what operation of the query was acquiring what lock
> when it deadlocked.

Are the involved queries not enough? Why? What would you like to
have?

--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-03-24 23:21:02 Re: Proposal: new ereport option "errdetail_log"
Previous Message Tom Lane 2008-03-24 23:15:04 Re: [pgsql-www] New email list for emergency communications