Re: Non-empty default log_line_prefix

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Non-empty default log_line_prefix
Дата
Msg-id 16348.1476286855@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: Non-empty default log_line_prefix  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Ответы Re: Non-empty default log_line_prefix  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Список pgsql-hackers
Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes:
> That still doesn't address what to do about syslog and eventlog users.
> We would need either a separate prefix setting for those, or maybe
> something like %q that says, skip to here if using syslog.  (I don't
> know eventlog, so I don't know if a common setting for syslog and
> eventlog would work.)

Meh.  Those aren't default log output targets, so I don't think the
default prefix needs to cater for them.  People who adjust one setting
can adjust the other too.

There would be some value in the complexity you're thinking of for
installations that log to multiple targets concurrently, but really,
who does that?  Most production installations already begrudge
the I/O volume for a single log target.
        regards, tom lane



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: [COMMITTERS] pgsql: Extend framework from commit 53be0b1ad to report latch waits.
Следующее
От: Christoph Berg
Дата:
Сообщение: Re: Non-empty default log_line_prefix