Re: WIP - syslogger infrastructure changes - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: WIP - syslogger infrastructure changes
Date
Msg-id F7186C85-D6A1-4147-A94C-568ECD0112FA@hagander.net
Whole thread Raw
In response to Re: WIP - syslogger infrastructure changes  (Itagaki Takahiro <itagaki.takahiro@oss.ntt.co.jp>)
Responses Re: WIP - syslogger infrastructure changes
List 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 by date:

Previous
From: Stefan Kaltenbrunner
Date:
Subject: Re: CommitFest 2009-09: Now In Progress
Next
From: Itagaki Takahiro
Date:
Subject: Re: WIP - syslogger infrastructure changes