Skip site navigation (1) Skip section navigation (2)

Re: Proposed p.tch for error locations

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Michael Glaesemann <grzm(at)myrealbox(dot)com>, pgsql-patches(at)postgreSQL(dot)org, pgsql-interfaces(at)postgreSQL(dot)org
Subject: Re: Proposed p.tch for error locations
Date: 2006-03-13 16:08:30
Message-ID: 7837.1142266110@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-interfacespgsql-patches
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Tom Lane wrote:
>> That information is already available to pgAdmin, and has been since
>> 7.4; if they are failing to exploit it that's their problem not libpq's.

> Aye, that's fine.  I don't really know if pgAdmin uses the info or not.
> I thought the proposal to remove the "at character N" in the error
> message meant that the only way to get that information would be from
> the "LINE Y: ...\n[some whitespace]^" message, which would be pretty
> cumbersome.

You should reflect on the fact that psql is currently generating that
line from outside libpq ...

			regards, tom lane

In response to

pgsql-patches by date

Next:From: Neil ConwayDate: 2006-03-13 18:05:19
Subject: Re: Fix syntax errors in contrib uninstall scripts
Previous:From: Andreas PflugDate: 2006-03-13 16:07:48
Subject: Re: CREATE SYNONYM ...

pgsql-interfaces by date

Next:From: Milen DzhumerovDate: 2006-03-13 18:27:38
Subject: Compiling/Linking on win32
Previous:From: Alvaro HerreraDate: 2006-03-13 16:03:35
Subject: Re: Proposed p.tch for error locations

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group