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

From Brendan Jurd
Subject Re: change name of redirect_stderr?
Date
Msg-id 37ed240d0708141357w74c54d44g1da22c5271db3ddd@mail.gmail.com
Whole thread Raw
In response to Re: change name of redirect_stderr?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 8/15/07, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> "Brendan Jurd" <direvus@gmail.com> writes:
> > The consistent prefix idea sounds good; does "logging_enable" jive
> > with your proposal?
>
> I dislike it.  I claim that logging to plain stderr (without the
> syslogger process) is still logging.  Logging to syslog (which also
> doen't need the syslogger process) is *definitely* logging.  Something
> named "logging_enable" would suggest to the normal person that without
> it turned on, you'll get *nothing*.
>
> I'm not wedded to "collector" per se, but you really cannot escape the
> fact that there is one more concept in here than you wish to admit.
> I think that reflecting the existence of a collector process in the GUC
> names makes things clearer, not less clear.

Fair enough.  I just took a fresh look at postmaster.conf, and indeed
the logging variables are more complex than I gave them credit for
with "logging_enable".  Retracted.


pgsql-hackers by date:

Previous
From: "Mike Rylander"
Date:
Subject: Re: tsearch2 in PostgreSQL 8.3?
Next
From: Decibel!
Date:
Subject: Re: [mmoncure@gmail.com: Re: [GENERAL] array_to_set functions]