Re: elog(LOG), elog(DEBUG)

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: elog(LOG), elog(DEBUG)
Date: 2001-05-07 16:45:47
Message-ID: 200105071645.f47GjlD11651@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Tom Lane writes:
>
> > Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> > > There's a TODO item to make elog(LOG) a separate level. I propose the
> > > name INFO. It would be identical to DEBUG in effect, only with a
> > > different label.
> >
> > This conveys nothing to my mind. How should I determine whether a given
> > elog call ought to use INFO or DEBUG?
>
> DEBUG is for messages intended to help locating and analyzing faults in
> the source code (i.e., debugging). Normal users don't need this during
> normal operation.
>
> INFO (or whatever the name) is for messages that administrator's might be
> interested in for auditing and tuning.

Seems like a good idea.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Trond Eivind =?iso-8859-1?q?Glomsr=F8d?= 2001-05-07 16:46:48 Re: File system performance and pg_xlog
Previous Message Vince Vielhaber 2001-05-07 16:45:44 Re: typo in psql's help