Re: Identifying function-lookup failures due to argument name mismatches

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Dominique Devienne <ddevienne(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Identifying function-lookup failures due to argument name mismatches
Date: 2025-09-15 21:12:38
Message-ID: 665947.1757970758@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Mon, Sep 15, 2025 at 4:01 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> The primary error message is not varying, only the DETAIL/HINT, so
>> I find this concern pretty far-fetched. Also, I believe that the
>> case that the message intends to help with is very common and so
>> it will save a lot of people time, more than enough to outweigh
>> any cases where it's perhaps un-optimal.

> I'm not entirely convinced, but you could well be right. I do like all
> the other detailed diagnostics, I think, I just wasn't sure about that
> one. But I'm not really here to argue, just giving my opinion.

Fair enough. Again, how shall we proceed? What I suggest is to
go ahead and push what I have, and if there's anything that's not
so great, hopefully we'll get feedback about it before v19 is
frozen.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2025-09-15 21:15:44 Re: plan shape work
Previous Message Robert Haas 2025-09-15 21:07:47 Re: plan shape work