Re: Proposed GUC Variable - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Proposed GUC Variable
Date
Msg-id 200208230424.g7N4OxA28610@candle.pha.pa.us
Whole thread Raw
In response to Re: Proposed GUC Variable  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Proposed GUC Variable  ("Christopher Kings-Lynne" <chriskl@familyhealth.com.au>)
List pgsql-hackers
Tom Lane wrote:
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > Someone asked for that recently, and the email is in my mailbox for
> > consideration.  I think it is a great idea, and we have
> > debug_query_string that holds the current query.
> 
> debug_query_string doesn't necessarily have a lot to do with the
> proximate cause of the error.  Consider queries issued by rules,
> triggers, plpgsql functions, etc.

Maybe.  I think giving the user the string that caused the error is
probably what they want, rather than a rule or trigger that they can't
tie back to an actual query.

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073
 


pgsql-hackers by date:

Previous
From: Lamar Owen
Date:
Subject: Re: v7.2.2 packaged ...
Next
From: "Christopher Kings-Lynne"
Date:
Subject: Another tsearch bug...