Received: from phc.net (smtp.phc.net [209.133.96.11]) by postgresql.org (Postfix) with ESMTP id 454E8475892; Fri, 12 Apr 2002 14:19:20 -0400 (EDT) Received: from phc.net (209.133.25.131) by phc.net with ESMTP (Eudora Internet Mail Server 3.0.3); Fri, 12 Apr 2002 11:19:20 -0700 Message-ID: <3CB72553.A7037D96@phc.net> Date: Fri, 12 Apr 2002 11:20:04 -0700 From: Richard Emberson X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.9-31 i686) X-Accept-Language: en MIME-Version: 1.0 To: Tom Lane Cc: Markus Wagner , pgsql-general@postgresql.org, pgsql-sql@postgresql.org Subject: Re: [SQL] how to get more detailed error messages? References: <0204120904101G.28384@magnus> <28259.1018633206@sss.pgh.pa.us> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200204/510 X-Sequence-Number: 23225 When an error occurs in the parser, have the parser inform the top-level (whatever that is) and the query is reparsed this time keeping the context information so that a more meaningful error message maybe generated. This has the overhead of setting up the catch block (I guess it would be a longjmp) and also the parser would have to check a flag to see if context information (backpointers) should be generated - unless you have two versions of the parser ... compile time flags. Richard Tom Lane wrote: > Markus Wagner writes: > > we have a union query over three select queries with some hundred lines of > > SQL code, created as a view. > > > When executing the code we get an error message "ERROR: UNION types "text" > > and "int4" not matched" with only the line number of the terminating > > semicolon included. > > > Isn't there a way to get the parser to talk more precisely??? > > Not at present. This sort of error comes from deep inside the parser; > the code is working with a querytree that does not have any direct > connection anymore to source text. Line numbers are not to be had, > and your suggestion of variable names is rather pointless also, at > least for this example --- there's no guarantee that the expressions > causing the problem involve any variables at all. > > I have occasionally toyed with the idea of labeling querytree elements > with back-pointers showing the segment of source text that they came > from, but AFAICT this would impose a nontrivial cost on parsing activity > --- a cost that'd be paid all the time, even on correct queries. Not > sure if it'd be a net benefit or not. > > regards, tom lane > > ---------------------------(end of broadcast)--------------------------- > TIP 5: Have you checked our extensive FAQ? > > http://www.postgresql.org/users-lounge/docs/faq.html