Re: Identifying function-lookup failures due to argument name mismatches
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Dominique Devienne <ddevienne@gmail.com>,
pgsql-hackers@lists.postgresql.org
Date: 2025-09-15T21:12:38Z
Lists: pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes: > On Mon, Sep 15, 2025 at 4:01 PM Tom Lane <tgl@sss.pgh.pa.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
Commits
-
Provide more-specific error details/hints for function lookup failures.
- 83a56419457e 19 (unreleased) landed