Re: change name of redirect_stderr?

From: "Brendan Jurd" <direvus(at)gmail(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Michael Glaesemann" <grzm(at)seespotcode(dot)net>, "Josh Berkus" <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: change name of redirect_stderr?
Date: 2007-08-14 20:57:16
Message-ID: 37ed240d0708141357w74c54d44g1da22c5271db3ddd@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 8/15/07, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Brendan Jurd" <direvus(at)gmail(dot)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.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Decibel! 2007-08-14 21:08:27 Re: [mmoncure@gmail.com: Re: [GENERAL] array_to_set functions]
Previous Message Mike Rylander 2007-08-14 20:47:13 Re: tsearch2 in PostgreSQL 8.3?