Re: Identifying function-lookup failures due to argument name mismatches - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Identifying function-lookup failures due to argument name mismatches
Date
Msg-id 1880721.1755875024@sss.pgh.pa.us
Whole thread Raw
In response to Re: Identifying function-lookup failures due to argument name mismatches  (Dominique Devienne <ddevienne@gmail.com>)
List pgsql-hackers
Dominique Devienne <ddevienne@gmail.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



pgsql-hackers by date:

Previous
From: Benoit T
Date:
Subject: Re: pg_stat_statements: Add `calls_aborted` counter for tracking query cancellations
Next
From: "Euler Taveira"
Date:
Subject: Re: Add support for specifying tables in pg_createsubscriber.