Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250]) by postgresql.org (Postfix) with ESMTP id 5151F475892; Fri, 12 Apr 2002 14:26:56 -0400 (EDT) Received: from [209.10.40.250] (account ) by davinci.ethosmedia.com (CommuniGate Pro WebUser 3.5.9) with HTTP id 1320638; Fri, 12 Apr 2002 11:26:55 -0700 From: "Josh Berkus" Subject: Re: [SQL] how to get more detailed error messages? To: Tom Lane , Markus Wagner Cc: pgsql-general@postgresql.org, pgsql-sql@postgresql.org X-Mailer: CommuniGate Pro Web Mailer v.3.5.9 Date: Fri, 12 Apr 2002 11:26:55 -0700 Message-ID: In-Reply-To: <28259.1018633206@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Archive-Number: 200204/596 X-Sequence-Number: 23311 Tom, > 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. I'd suggest it as a compile-time option, if that's feasable. This is only a concern, IME, for development machines. On a production machine, presumably all of the queries and functions are already tested. Thus, if we had the compile-time option of --explicit-query-errors then it would add this functionality for testers without slowing down PostgreSQL overall. Don't know if compile-time options for the parser are reasonable, though. Also, I would personally rate this below several other improvement projects in priority, such as in-database replication, point-in-time recovery and nested transactions. -Josh Berkus