Re: elog() patch

Поиск
Список
Период
Сортировка
Искать
От
Peter Eisentraut
Тема
Re: elog() patch
Дата
Msg-id
Pine.LNX.4.30.0203011303160.687-100000@peter.localdomain
Ответ на
Re: elog() patch (Zeugswetter Andreas SB SD)
Список
Дерево обсуждения
Re: elog() patch "Zeugswetter Andreas SB SD" <ZeugswetterA@spardat.at>
Re: elog() patch Bruce Momjian <pgman@candle.pha.pa.us>
Re: elog() patch Tom Lane <tgl@sss.pgh.pa.us>
Re: elog() patch Bruce Momjian <pgman@candle.pha.pa.us>
Re: elog() patch Tom Lane <tgl@sss.pgh.pa.us>
Re: elog() patch Bruce Momjian <pgman@candle.pha.pa.us>
Zeugswetter Andreas SB SD 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.

-- 
Peter Eisentraut   peter_e@gmx.net


В списке pgsql-hackers по дате отправления
От: Justin Clift
Дата:
Сообщение: Re: Database Caching
От: Bruce Momjian
Дата:
Сообщение: Re: elog() patch
FAQ