Re: WIP - syslogger infrastructure changes
От | Magnus Hagander |
---|---|
Тема | Re: WIP - syslogger infrastructure changes |
Дата | |
Msg-id | F7186C85-D6A1-4147-A94C-568ECD0112FA@hagander.net обсуждение исходный текст |
Ответ на | Re: WIP - syslogger infrastructure changes (Itagaki Takahiro <itagaki.takahiro@oss.ntt.co.jp>) |
Ответы |
Re: WIP - syslogger infrastructure changes
|
Список | pgsql-hackers |
On 15 sep 2009, at 07.21, Itagaki Takahiro <itagaki.takahiro@oss.ntt.co.jp > wrote: > > Magnus Hagander <magnus@hagander.net> wrote: > >> Second, data transfer from the backends is now in the form of >> structured data, and the actual logging message is put together in >> the >> syslogger > > I'd like to have an opposite approach -- per-backend log files. > Syslogger and appending logs at only one file will be a performance > bottleneck when we want write a lot of logs. Per-backend log files > like "postgres.<backend-id>.log" would be a help then. > That would make the log more or less completely useless for any of the situations I've been in. I can see each backend writing it, certainly, but keeping it in separate files makes it useless without post processing, which in most vases means useless for day-to-day work. /Magnus
В списке pgsql-hackers по дате отправления: