From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Franck Verrot <franck(at)verrot(dot)fr> |
Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Kuntal Ghosh <kuntalghosh(dot)2007(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Mention column name in error messages |
Date: | 2016-11-06 21:13:23 |
Message-ID: | 1299.1478466803@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Franck Verrot <franck(at)verrot(dot)fr> writes:
> On Sat, Nov 5, 2016 at 11:13 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> The cases that are successfully annotated by the current patch seem to
>> mostly already have error cursor information, which really is good enough
>> IMO --- you can certainly figure out which column corresponds to the
>> textual spot that the cursor is pointing at.
> The original intent of that patch tried to cover the case where we insert
> records
> made of dozens columns sharing the same type definition, and trying to
> understand
> what is going on, at a glance, when we debugged something like this:
> ...
> Relying on the cursor seems to be of little help I'm afraid.
Well, it would be an improvement over what we've got now. Also, a feature
similar to what I suggested would help in localizing many types of errors
that have nothing to do with coercion to a target column type.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Shay Rojansky | 2016-11-06 21:40:38 | Re: macaddr 64 bit (EUI-64) datatype support |
Previous Message | Stefan Scheid | 2016-11-06 21:08:01 | Fwd: Re: [CORE] temporal tables (SQL2011) |