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

From: Peter T Mount <psqlhack(at)maidast(dot)demon(dot)co(dot)uk>
To: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
Cc: "Vadim B(dot) Mikheev" <vadim(at)sable(dot)krasnoyarsk(dot)su>, 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-04 12:16:08
Message-ID: Pine.LNX.3.95.980104121118.18896A-100000@maidast
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On Sat, 3 Jan 1998, Bruce Momjian wrote:

> Sounds maybe a little too serious. We currently use WARN a lot to
> indicate errors in the supplied SQL statement. Perhaps we need to make
> the parser elog's ERROR, and the non-parser WARN's ABORT? Is that good?
> When can I make the change? I don't want to mess up people's current work.

This shouldn't affect JDBC. The only thing that would break things, is if
the notification sent by the "show datestyle" statement is changed.

--
Peter T Mount petermount(at)earthling(dot)net or pmount(at)maidast(dot)demon(dot)co(dot)uk
Main Homepage: http://www.demon.co.uk/finder
Work Homepage: http://www.maidstone.gov.uk Work EMail: peter(at)maidstone(dot)gov(dot)uk

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter T Mount 1998-01-04 12:39:39 Re: [HACKERS] Re: [QUESTIONS] tuple is too big?
Previous Message The Hermit Hacker 1998-01-04 07:26:34 New Snapshot(s)