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

Поиск
Список
Период
Сортировка
От Bruce Momjian
Тема Re: Error messages/logging (Was: Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/backend/parser gram.y parse_oper.c')
Дата
Msg-id 199801051727.MAA15860@candle.pha.pa.us
обсуждение исходный текст
Ответ на Re: Error messages/logging (Was: Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/backend/parser gram.y parse_oper.c')  ("Vadim B. Mikheev" <vadim@sable.krasnoyarsk.su>)
Список 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 по дате отправления:

Предыдущее
От: Constantin Teodorescu
Дата:
Сообщение: I want to change libpq and libpgtcl for better handling of large query results
Следующее
От: Bruce Momjian
Дата:
Сообщение: Re: Error messages/logging (Was: Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/backend/parser gram.y parse_oper.c')