Re: change name of redirect_stderr?

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: change name of redirect_stderr?
Date: 2007-08-14 15:36:59
Message-ID: 200708141537.l7EFb0303797@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Dunstan wrote:
>
>
> Tom Lane wrote:
> > Andrew Dunstan <andrew(at)dunslane(dot)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(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2007-08-14 15:38:33 Re: [mmoncure@gmail.com: Re: [GENERAL] array_to_set functions]
Previous Message Bruce Momjian 2007-08-14 15:22:05 Re: GUC for default heap fillfactor