Re: change name of redirect_stderr?
От | Bruce Momjian |
---|---|
Тема | Re: change name of redirect_stderr? |
Дата | |
Msg-id | 200708141537.l7EFb0303797@momjian.us обсуждение исходный текст |
Ответ на | Re: change name of redirect_stderr? (Andrew Dunstan <andrew@dunslane.net>) |
Ответы |
Re: change name of redirect_stderr?
|
Список | pgsql-hackers |
Andrew Dunstan wrote: > > > 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". Are we trying to use log_* prefixes, e.g. log_start_collector? -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. +
В списке pgsql-hackers по дате отправления: