X-Original-To: pgsql-interfaces-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 839FD9DCCD0; Mon, 13 Mar 2006 12:08:36 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 75966-05; Mon, 13 Mar 2006 12:08:34 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 203A49DCC69; Mon, 13 Mar 2006 12:08:32 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id k2DG8U5V007838; Mon, 13 Mar 2006 11:08:30 -0500 (EST) To: Alvaro Herrera cc: Michael Glaesemann , pgsql-patches@postgreSQL.org, pgsql-interfaces@postgreSQL.org Subject: Re: Proposed p.tch for error locations In-reply-to: <20060313160335.GN8274@surnet.cl> References: <5114.1142185055@sss.pgh.pa.us> <7274.1142262691@sss.pgh.pa.us> <20060313153209.GA15002@surnet.cl> <7693.1142265427@sss.pgh.pa.us> <20060313160335.GN8274@surnet.cl> Comments: In-reply-to Alvaro Herrera message dated "Mon, 13 Mar 2006 12:03:35 -0400" Date: Mon, 13 Mar 2006 11:08:30 -0500 Message-ID: <7837.1142266110@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.112 required=5 tests=[AWL=0.112] X-Spam-Score: 0.112 X-Spam-Level: X-Archive-Number: 200603/14 X-Sequence-Number: 6070 Alvaro Herrera 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