Re: change name of redirect_stderr? - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: change name of redirect_stderr?
Date
Msg-id 200708141537.l7EFb0303797@momjian.us
Whole thread Raw
In response to Re: change name of redirect_stderr?  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: change name of redirect_stderr?  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-hackers
Andrew Dunstan wrote:
> 
> 
> Tom Lane wrote:
> > Andrew Dunstan <andrew@dunslane.net> writes:
> >   
> >> Before I wrap up the CSVlog stuff, we need to decide whether or not to 
> >> change the name of the redirect_stderr setting, and if so to what. The 
> >> reason is that with CSVlogs it will no longer apply just to stderr (we 
> >> will require it to be on for CSVlogs, in fact).
> >>     
> >
> >   
> >> I suggest "redirect_logs", although it's arguably too general as it 
> >> doesn't apply to syslog/eventlog.
> >>     
> >
> > Perhaps it should be named analogously to stats_start_collector,
> > ie think of the syslogger process as a "log collector".  I don't
> > much like "log_start_collector" though --- "start_log_collector"
> > seems far less confusing as to where the verb is.
> >
> >
> >   
> 
> Nobody else seems to care much. I'll go with "start_log_collector".

Are we trying to use log_* prefixes, e.g. log_start_collector?

--  Bruce Momjian  <bruce@momjian.us>          http://momjian.us EnterpriseDB
http://www.enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: GUC for default heap fillfactor
Next
From: "Pavel Stehule"
Date:
Subject: Re: [mmoncure@gmail.com: Re: [GENERAL] array_to_set functions]