Re: [SQL] how to get more detailed error messages?

From: "Josh Berkus" <josh(at)agliodbs(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Markus Wagner <wagner(at)imsd(dot)uni-mainz(dot)de>
Cc: pgsql-general(at)postgresql(dot)org, pgsql-sql(at)postgresql(dot)org
Subject: Re: [SQL] how to get more detailed error messages?
Date: 2002-04-12 18:26:55
Message-ID: web-1320638@davinci.ethosmedia.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-sql

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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Josh Berkus 2002-04-12 19:00:19 Proposal: New Mailing List
Previous Message Richard Emberson 2002-04-12 18:20:04 Re: [SQL] how to get more detailed error messages?

Browse pgsql-sql by date

  From Date Subject
Next Message Tom Lane 2002-04-12 18:28:11 Re: Functions in Postgres
Previous Message Richard Emberson 2002-04-12 18:20:04 Re: [SQL] how to get more detailed error messages?