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

From: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
To: vadim(at)sable(dot)krasnoyarsk(dot)su (Vadim B(dot) Mikheev)
Cc: matti(at)algonet(dot)se, hackers(at)postgresql(dot)org
Subject: Re: Error messages/logging (Was: Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/backend/parser gram.y parse_oper.c')
Date: 1998-01-05 17:27:53
Message-ID: 199801051727.MAA15860@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)candle(dot)pha(dot)pa(dot)us

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Constantin Teodorescu 1998-01-05 18:43:45 I want to change libpq and libpgtcl for better handling of large query results
Previous Message Vadim B. Mikheev 1998-01-05 17:12:38 Re: Error messages/logging (Was: Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/backend/parser gram.y parse_oper.c')