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

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

Dominique Devienne <ddevienne(at)gmail(dot)com> writes:
> One last though. Is it worth reserving a few bits to count the
> candidate matches? You'll never reach 32 flags, so 8 feels like plenty.
> Barring listing the candidates, a count hint might help? In my case
> it was only 1, but it more complete cases where the search_path
> is involved, one might get surprised with candidates coming from afar
> making things ambiguous? Again, jus thinking aloud. --DD

Candidates in what sense, that is where would you make the count?
In any case, that seems like it's about adding detail to the
"ambiguous function" case, which might be worth doing but it's
not the goal of this patch.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Euler Taveira 2025-08-22 15:26:29 Re: Add support for specifying tables in pg_createsubscriber.
Previous Message Benoit T 2025-08-22 14:58:16 Re: pg_stat_statements: Add `calls_aborted` counter for tracking query cancellations