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

From Bruce Momjian
Subject Re: Error messages/logging (Was: Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/backend/parser gram.y parse_oper.c')
Date
Msg-id 4b9a0a0a4be345f01a0db55371e6ad5f
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
> > This generates an ERROR, because the parser catches the type mismatch.
>
> Hm - this is just example, I could use casting here...

Ah, you got me here.  If you cast int2(), you would get a different
message.  You are right.

I changes parser/, commands/, utils/adt/, and several of the /tcop
files.  Should take care of most of them.  Any errors coming out of the
optimizer or executor, or cache code should be marked as serious.  Let's
see if it helps.  I can easily make them all the same.

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

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

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