Skip site navigation (1) Skip section navigation (2)

Re: Log rotation?

From: Matthew Hagerty <mhagerty(at)voyager(dot)net>
To: Ian Lance Taylor <ian(at)airs(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Log rotation?
Date: 2001-09-06 14:08:21
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
At 08:54 PM 9/5/2001 -0700, Ian Lance Taylor wrote:
>Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> > > And no, "use syslog" doesn't count.
> >
> > Why not?
>The standard implementations of syslog lose log entries under heavy
>load, because they rely on a daemon which reads from a named pipe with
>a limited buffer space.  This is not acceptable in a production
>system, since heavy load is often just the time you need to see the
>log entries.
>It would be possible to implement the syslog(3) interface in a
>different way, of course, which did not use syslogd.  I don't know of
>any such implementation.
>(My personal preference these days is an approach like DJB's
>daemontools, which separates the handling of log entries from the
>program doing the logging.)


Kind of ironic, I have been working on a similar logging system for Apache 
that works with PostgreSQL, and I just released 2.0-beta last night.  My 
post to announcements was delayed, but you can check it out here:

If pgLOGd looks like something similar to what you are looking for, I could 
probably modify it to log for PostgreSQL.  Two of its requirements during 
development were fast and robust, and similar to what you described above 
it does not "process" the entries, that is done later.  You also got me 
thinking that maybe syslogd needs an overhaul too...


In response to


pgsql-hackers by date

Next:From: Denis PerchineDate: 2001-09-06 14:09:07
Subject: Re: Problems starting up postgres
Previous:From: Tom LaneDate: 2001-09-06 13:51:54
Subject: Re: Log rotation?

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group