From: | "John Hansen" <john(at)geeknet(dot)com(dot)au> |
---|---|
To: | <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Log rotation |
Date: | 2004-03-14 19:02:27 |
Message-ID: | 5066E5A966339E42AA04BA10BA706AE56160@rodrick.geeknet.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
My $0.02 worth: syslog-ng
:)
Regards,
John
-----Original Message-----
From: pgsql-hackers-owner(at)postgresql(dot)org
[mailto:pgsql-hackers-owner(at)postgresql(dot)org] On Behalf Of Bruce Momjian
Sent: Monday, March 15, 2004 5:50 AM
To: Tom Lane
Cc: Fernando Nasser; Lamar Owen; pgsql-hackers(at)postgresql(dot)org
Subject: Re: [HACKERS] Log rotation
Tom Lane wrote:
> Fernando Nasser <fnasser(at)redhat(dot)com> writes:
> > Lamar Owen wrote:
> >> Third, it seems that you don't have enough profiling data to
> >> support a 'syslog is bad' position.
>
> > That is true. It is from hearsay, from people who run production
> > environments. It may be a belief based on old experiences though.
>
> I think it's pretty well established that syslog sucks for high log
> volume if you run it in the mode where it fsyncs its log after every
> message. But I don't believe we have any data that says it's a
> problem even if you avoid that pitfall.
What versions of syslog fsync, and where is the syslog.conf option. I
don't see it on FreeBSD or Linux.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania
19073
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if
your
joining column's datatypes do not match
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2004-03-14 19:09:49 | Re: Log rotation |
Previous Message | Tom Lane | 2004-03-14 18:59:54 | Re: Log rotation |