Re: Error messages/logging (Was: Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/backend/parser gram.y parse_oper.c')

Bruce Momjian <maillist@candle.pha.pa.us>

From: Bruce Momjian <maillist@candle.pha.pa.us>
To: vadim@sable.krasnoyarsk.su (Vadim B. Mikheev)
Cc: matti@algonet.se, hackers@postgreSQL.org
Date: 1998-01-05T03:25:03Z
Lists: pgsql-hackers
> ABORT means that transaction is ABORTed.
> Will ERROR mean something else ?
> Why should we use two different flag-words for the same thing ?
> Note, that I don't object against using ERROR, but against using two words.

I wanted two words to distinguish between user errors like a mis-spelled
field name, and internal errors like btree failure messages.

Make sense?

I made all the error messages coming from the parser as ERROR, and
non-parser messages as ABORT.  I think I will need to fine-tune the
messages because I am sure I missed some messages that should be ERROR
but are ABORT.  For example, utils/adt messages about improper data
formats, is that an ERROR or an ABORT?

-- 
Bruce Momjian
maillist@candle.pha.pa.us