Re: Better handling of parse errors

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Gavin Sherry <swm(at)linuxworld(dot)com(dot)au>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Better handling of parse errors
Date: 2002-08-14 05:44:05
Message-ID: 5263.1029303845@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Gavin Sherry <swm(at)linuxworld(dot)com(dot)au> writes:
> ... do we want to modify every 7.2 error message?

Nyet ... but I don't think tacking an offset onto the end of
"parse error at or near foo" messages is likely to cause the
sort of generalized havoc you suggest ...

I'm on record as favoring a thorough redesign of the error-reporting
facility, and I hope to see that happen in conjunction with a frontend
protocol change in 7.4. But I think your proposed change in this patch
is fairly harmless and could be done now.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2002-08-14 05:45:45 Re: CLUSTER all tables at once?
Previous Message Gavin Sherry 2002-08-14 05:35:47 Re: [HACKERS] CREATE TEMP TABLE .... ON COMMIT

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2002-08-14 05:47:57 Re: improve FOUND in PL/PgSQL
Previous Message Bruce Momjian 2002-08-14 05:43:18 Re: libpgtcl modifications