Re: Proposed GUC Variable - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Proposed GUC Variable
Date
Msg-id 200208272114.g7RLEhj19518@candle.pha.pa.us
Whole thread Raw
In response to Re: Proposed GUC Variable  (Larry Rosenman <ler@lerctr.org>)
Responses Re: Proposed GUC Variable  (Larry Rosenman <ler@lerctr.org>)
List pgsql-hackers
Larry Rosenman wrote:
> > But we should have some default to print some of the query, because
> > right now we print none of it. I am not saying it is perfect, but it is
> > better than what we have, and is a reasonable default.
> On an error, you may not be able to reproduce it.  Why not print the
> whole query to the log?
> 
> I don't see a reason for truncating it at 80 chars. 
> 
> IMHO, of course. 

Because every typo query, every syntax error of a user in psql would
appear in your logs.  That seems excessive.  Already the ERROR line
appears in the logs.  Do we want to see their bad query too?

My concern is that long queries could easily bulk up the logs to the
point where the actual important log messages would be lost in the fog.


--  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: Bruce Momjian
Date:
Subject: Re: [BUGS] Bug #718: request for improvement of /? to show
Next
From: Bruce Momjian
Date:
Subject: Re: SET SCHEMA?