From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: change name of redirect_stderr? |
Date: | 2007-08-10 21:34:07 |
Message-ID: | 46BCD9CF.1020909@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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".
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-08-10 22:52:36 | Re: regexp_split_to_array hangs backend |
Previous Message | Sergiy Vyshnevetskiy | 2007-08-10 20:03:10 | Re: crypting prosrc in pg_proc |