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

From: "Vadim B(dot) Mikheev" <vadim(at)sable(dot)krasnoyarsk(dot)su>
To: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
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:12:38
Message-ID: 34B11486.AFE716EE@sable.krasnoyarsk.su
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian wrote:
>
> > > 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?
> >
> > Good question :)
> >
> > Following your way
> >
> > insert into X (an_int2_field) values (9999999999);
> >
> > should cause ERROR message, but
> >
> > insert into X (an_int2_field) select an_int4_field from Y;
>
> This generates an ERROR, because the parser catches the type mismatch.

Hm - this is just example, I could use casting here...

Vadim

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 1998-01-05 17:27:53 Re: Error messages/logging (Was: Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/backend/parser gram.y parse_oper.c')
Previous Message Bruce Momjian 1998-01-05 16:10:37 Re: Error messages/logging (Was: Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/backend/parser gram.y parse_oper.c')