From: Josh Berkus <josh@agliodbs.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: Markus Wagner <wagner@imsd.uni-mainz.de>
Cc: pgsql-general@postgresql.org
Cc: pgsql-sql@postgresql.org
Subject: Re: [SQL] how to get more detailed error messages?
Date: Fri, 12 Apr 2002 11:26:55 -0700
Message-ID: <web-1320638@davinci.ethosmedia.com> (raw)
In-Reply-To: <28259.1018633206@sss.pgh.pa.us>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: josh@agliodbs.com, tgl@sss.pgh.pa.us, wagner@imsd.uni-mainz.de, pgsql-general@postgresql.org
Subject: Re: [SQL] how to get more detailed error messages?
In-Reply-To: <web-1320638@davinci.ethosmedia.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox