Re: Proposed GUC Variable - Mailing list pgsql-hackers

From Ross J. Reedstrom
Subject Re: Proposed GUC Variable
Date
Msg-id 20020827223004.GA20278@rice.edu
Whole thread Raw
In response to Re: Proposed GUC Variable  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Proposed GUC Variable
Re: Proposed GUC Variable
List pgsql-hackers
On Tue, Aug 27, 2002 at 06:08:40PM -0400, 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 agree that a 'trimmed' query is likely to be useless, but the idea of
printing the query on ERROR is a big win for me: right now I'm logging
_all_ queries on our development machine (and sometimes on our production
machine. when there's trouble) so my logs would get considerably smaller.

A settable trim length would probably be a good idea, I suppose, for
those slinging 'bytea' and toasted texts around.

Ross


pgsql-hackers by date:

Previous
From: Marc Lavergne
Date:
Subject: Re: C vs. C++ contributions
Next
From: Larry Rosenman
Date:
Subject: Re: Proposed GUC Variable