This is an intersting mix of features. First, use LOG so it goes only
to the log file by default _but_ can be turned on to be seen by the
client, and remove the GUC completely.
This does make 100% sense because an ERROR is going to go the client and
the server logs by default, and LOG is going to go to the server logs by
default _but_ can optionally be seen by the client by modifying
min_client_messagses.
---------------------------------------------------------------------------
Christopher Kings-Lynne wrote:
> So long as the change is only evident in the log, I agree.
>
> Chris
>
> > -----Original Message-----
> > From: pgsql-hackers-owner@postgresql.org
> > [mailto:pgsql-hackers-owner@postgresql.org]On Behalf Of Markus Bertheau
> > Sent: Friday, 23 August 2002 3:55 PM
> > To: Bruce Momjian
> > Cc: Christopher Kings-Lynne; Hackers
> > Subject: Re: [HACKERS] Proposed GUC Variable
> >
> >
> > On Fri, 2002-08-23 at 04:46, Bruce Momjian wrote:
> > >
> > > * Add GUC parameter to print queries that generate errors
> >
> > Maybe don't make that an option, but rather do it always. I don't see
> > where that would hurt. And killing configuration options that are
> > unneeded is always a Good Thing.
> >
> > --
> > Markus Bertheau.
> > Berlin, Berlin.
> > Germany.
> >
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 6: Have you searched our list archives?
> >
> > http://archives.postgresql.org
> >
>
>
-- 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
