Re: Log rotation

Поиск
Список
Период
Сортировка
От John Hansen
Тема Re: Log rotation
Дата
Msg-id 5066E5A966339E42AA04BA10BA706AE56160@rodrick.geeknet.com.au
обсуждение исходный текст
Ответ на Log rotation  (Fernando Nasser <fnasser@redhat.com>)
Список pgsql-hackers
My $0.02 worth: syslog-ng

:)

Regards,

John

-----Original Message-----
From: pgsql-hackers-owner@postgresql.org
[mailto:pgsql-hackers-owner@postgresql.org] On Behalf Of Bruce Momjian
Sent: Monday, March 15, 2004 5:50 AM
To: Tom Lane
Cc: Fernando Nasser; Lamar Owen; pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Log rotation

Tom Lane wrote:
> Fernando Nasser <fnasser@redhat.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@candle.pha.pa.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




В списке pgsql-hackers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: Log rotation
Следующее
От: Bruce Momjian
Дата:
Сообщение: Re: Log rotation