| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: change name of redirect_stderr? |
| Date: | 2007-08-09 17:58:21 |
| Message-ID: | 17922.1186682301@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
No strong opinion here, just tossing out some ideas.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | tomas | 2007-08-09 18:04:18 | Re: default_text_search_config and expression indexes |
| Previous Message | Tom Lane | 2007-08-09 17:14:34 | Re: HOT patch, missing things |