Re: elog() patch - Mailing list pgsql-hackers

From Zeugswetter Andreas SB SD
Subject Re: elog() patch
Date
Msg-id 46C15C39FEB2C44BA555E356FBCD6FA41EB533@m0114.s-mxs.net
Whole thread Raw
In response to elog() patch  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
Peter writes:
> > I am referring to "completion condition" messages according
> to SQLSTATE:
> >
> > 00xxx:    Success
>
> This is an INFO (or no message at all).  The idea was that things like the
> automatic index creation for a PK would be INFO, and you could easily turn
> off INFO somehow.
>
> > 01xxx:    Success with Warning
>
> This is a NOTICE.
>
> > 02xxx:    Success but no rows found
>
> This is nothing special.
>
> > 03 and > :    Failure
>
> This is is ERROR or above.
>
> > I see that there is no notion of INFO, thus I agree that INFO should not be
> > something normally sent to the user. INFO could be the first DEBUG Level,
> > or completely skipped.
>
> It's sort of the "tip" level.  A lot of people don't like to see them, so
> it's reasonable to separate them from NOTICE.  You could think of them as
> first debug level, if you like.

All agreed, matches what I was trying to say. Only I like the keyword
WARNING more than NOTICE.

Andreas


pgsql-hackers by date:

Previous
From: "Zeugswetter Andreas SB SD"
Date:
Subject: Re: elog() patch
Next
From: Jean-Paul ARGUDO
Date:
Subject: Re: Oracle vs PostgreSQL in real life : NEWS!!!