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

From Andrew Dunstan
Subject Re: change name of redirect_stderr?
Date
Msg-id 46BCD9CF.1020909@dunslane.net
Whole thread Raw
In response to Re: change name of redirect_stderr?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: change name of redirect_stderr?  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers

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".

cheers

andrew


pgsql-hackers by date:

Previous
From: Sergiy Vyshnevetskiy
Date:
Subject: Re: crypting prosrc in pg_proc
Next
From: Tom Lane
Date:
Subject: Re: regexp_split_to_array hangs backend