Re: [HACKERS] Proposed GUC Variable - Mailing list pgsql-patches

From Gavin Sherry
Subject Re: [HACKERS] Proposed GUC Variable
Date
Msg-id Pine.LNX.4.21.0208281618300.23917-102000@linuxworld.com.au
Whole thread Raw
Responses Re: [HACKERS] Proposed GUC Variable  ("Christopher Kings-Lynne" <chriskl@familyhealth.com.au>)
Re: [HACKERS] Proposed GUC Variable  (Peter Eisentraut <peter_e@gmx.net>)
Re: [HACKERS] Proposed GUC Variable  (Robert Treat <xzilla@users.sourceforge.net>)
List pgsql-patches
On Wed, 28 Aug 2002, Gavin Sherry wrote:

> On Tue, 27 Aug 2002, Tom Lane wrote:
>
> > Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > > But we should have some default to print some of the query,
> >
> > Why?  So far you've been told by two different people (make that three
> > now) that such a behavior is useless, and no one's weighed in in its
> > favor ...
>
> I completely agree. Nothing wrong with adding another guc variable and
> since it is a debug variable people expect lots of verbosity.

Attached is the patch. debug_print_error_query is set to false by default.

For want of a better phrase, I've prepended 'original query: ' to the
error message to highlight why it is in the log.

Gavin

Attachment

pgsql-patches by date:

Previous
From: Joe Conway
Date:
Subject: Anonymous-record-types omission
Next
From: Neil Conway
Date:
Subject: Re: rules regression test fix