Re: vpath builds and verbose error messages

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: vpath builds and verbose error messages
Date: 2011-11-18 13:35:03
Message-ID: 1321623145-sup-2804@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Noah Misch 2011-11-18 13:37:43 Re: RangeVarGetRelid()
Previous Message Albe Laurenz 2011-11-18 13:04:15 Review for "Add permission check on SELECT INTO"