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

From Thomas G. Lockhart
Subject Re: Error messages/logging (Was: Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/backend/parser gram.y parse_oper.c')
Date
Msg-id c5872b1c02333643a4338de1d7feb250
Whole thread Raw
In response to Error messages/logging (Was: Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/backend/parser gram.y parse_oper.c')  (Mattias Kregert <matti@algonet.se>)
List pgsql-hackers
> > > I wanted two words to distinguish between user errors like a mis-spelled
> > > field name, and internal errors like btree failure messages.
> > >
> > > Make sense?
> >
> > No, for me. Do Informix, Oracle, etc use two words ?
> > What benefit of special "in-parser-error" word for user - in any case
> > user will read error message itself to understand what caused error.
>
> OK, if no one likes my idea in the next day, I will make them all ERROR.

Well, _I_ like your idea. Seems like we can distinguish between operator error
(which the operator can fix) and internal problems, and we could flag them
differently. Perhaps there are so many grey areas that this becomes difficult to
do??

                                                    - Tom

------------------------------

pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Error messages/logging (Was: Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/backend/parser gram.y parse_oper.c')
Next
From: Bruce Momjian
Date:
Subject: Re: consttraints.source