Patrick Welche wrote:
> On Sat, Mar 13, 2004 at 10:36:23AM -0500, Fernando Nasser wrote:
>
>>Lamar Owen wrote:
>>
>>>Ok, riddle me this:
>>>
>>>If I have PostgreSQL set to log to syslog facility LOCAL0, and a
>>>local0.none on /var/log/messages and local0.* to /var/log/pgsql (assuming
>>>only one postmaster, unfortunately) then you get a flat file.
>>
>>The problem is that sysloging has more overhead than a plain append to a
>>file. There are some very strict response time AppServer applications
>>where we want to keep this things out of the picture.
>
>
> I thought it was an advantage to say "log to that box running syslog over
> there and leave my disk alone" - what do you have in mind with "AppServer
> applications" ?
>
And add more packets to the network, buffering etc.? I don't think so.
There are some applicatons which run in servers with very strict
response times and any syscall, network packet that can be saved counts.
>
>>It may be desirable to logrotate them at different times as well, so
>>they would have to be in different files.
>
>
> syslogd with newsyslog, just like any other log file? I must be missing
> something.. I don't see why postgresql is different..
>
The number of generated messgaes.
Maybe that is an area that can be worked on, i.e. reducing log
verbosity. Is 7.4.x much better than 7.3.x in that respect?
--
Fernando Nasser
Red Hat Canada Ltd. E-Mail: fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario M4P 2C9
