Re: vpath builds and verbose error messages - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: vpath builds and verbose error messages
Date
Msg-id 1321623145-sup-2804@alvh.no-ip.org
Whole thread Raw
In response to vpath builds and verbose error messages  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: vpath builds and verbose error messages
List pgsql-hackers
Excerpts from Peter Eisentraut's message of vie nov 18 01:34:18 -0300 2011:
> When using verbose error messages (psql \set VERBOSITY verbose) with a
> vpath build, you get this sort of thing:
>
> ERROR:  42703: column "foo" does not exist
> LINE 1: select foo;
>                ^
> LOCATION:  transformColumnRef,
/build/buildd-postgresql-9.1_9.1.1-3-i386-AP0ovQ/postgresql-9.1-9.1.1/build/../src/backend/parser/parse_expr.c:766
>
> Can we shorten that path somehow?  Either in the C code when printing it
> out, or during the build.  Any ideas?

Huh, I hadn't noticed, even though I see those all the time.  I agree
with shortening the path so that it's relative to the root source dir,
if that's what you propose:

LOCATION:  transformColumnRef, src/backend/parser/parse_expr.c:766

If it can be done at build time that would be best, because we wouldn't
be carrying thousands of useless copies of the source path ...  I have
no suggestions on how to do this, however.

--
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support


pgsql-hackers by date:

Previous
From: "Albe Laurenz"
Date:
Subject: Review for "Add permission check on SELECT INTO"
Next
From: Noah Misch
Date:
Subject: Re: RangeVarGetRelid()