Re: Documented parameter names differ from callable proargnames for several built-ins

I came across named parameters in an example of the pattern matching
chapter. I thought it was just an example but it turns out that it is
supported.

To inspect if each function parameter is documented correctly for each
function of each supported release seems like a gargantuan task to be
done.

Perhaps a note in somewhere that says "named parameters in functions
are supported but may not be up to date, using positional arguments is
the recommended way for function calling"?

On Sun, Nov 1, 2026 at 2:51 PM Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
>
> On Sat, Oct 31, 2026 at 6:50 PM Mi cro <micro6947(at)gmail(dot)com> wrote:
> > I suggest updating the displayed names to the SQL-visible parameter names.
> > Renaming the runtime parameters would change named-call compatibility.
>
> Thanks for the report and suggestion!
>
> I also found the same issue in pg_input_error_info(), ts_parse(), and ts_stat().
> The attached patch fixes the reported issue and updates these three functions
> as well.
>
> Regards,
>
> --
> Fujii Masao