Re: elog() patch

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Thomas Lockhart <lockhart(at)fourpalms(dot)org>
Cc: Zeugswetter Andreas SB SD <ZeugswetterA(at)spardat(dot)at>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: elog() patch
Date: 2002-03-01 20:37:00
Message-ID: 200203012037.g21Kb0302250@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Thomas Lockhart wrote:
> ...
> > My take was to have WARNING and NOTICE, yours is WARNING and INFO ?
> > For me INFO is also better to understand than NOTICE.
> > Not sure that alone is worth the change though, since lots of
> > clients will currently parse "NOTICE".
>
> fwiw, I find the connotations of these terms to be, in increasing order
> of severity:
>
> INFO, NOTICE, WARNING
>
> though the distinction between INFO and NOTICE is not so great that one
> absolutely could not replace the other.

Yes, that was my thought to. I am not sure we have any need for NOTICE
when we have INFO and WARNING. The NOTICE sort of kept both meanings,
and we don't need that anymore.

On a humorous note, when we got the code from Berkeley, WARN was the
original tag to error out a query.

--
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 Bruce Momjian 2002-03-01 20:42:04 Re: elog() patch
Previous Message Rod Taylor 2002-03-01 20:22:19 Re: eWeek Poll: Which database is most critical to your