From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Franck Verrot <franck(at)verrot(dot)fr> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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-29 04:37:44 |
Message-ID: | CAB7nPqT5G1QfvVpT1cHpfLyB7702nu29Qth-C0fUaErKnoo45w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Nov 7, 2016 at 10:26 AM, Franck Verrot <franck(at)verrot(dot)fr> wrote:
>
>
> On Sun, Nov 6, 2016 at 1:13 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>
>> > 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.
>
>
> Yes, it's a neat improvement in any case.
I have marked this patch as "Returned with Feedback" as it got its
share of reviews.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Langote | 2016-11-29 04:49:33 | Thinko in set_rel_consider_parallel() |
Previous Message | Michael Paquier | 2016-11-29 04:36:21 | Re: Password identifiers, protocol aging and SCRAM protocol |