Re: No function matches the given name and argument types.

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: arons <arons7(at)gmail(dot)com>
Cc: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: No function matches the given name and argument types.
Date: 2023-01-16 17:53:04
Message-ID: CAKFQuwYn04CjHEAbgH60TE5E3JRHZey_eu0q3_jD5r4db5HcSg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Jan 16, 2023 at 10:42 AM arons <arons7(at)gmail(dot)com> wrote:

> Why the error happen is clear to me, in the example is also easy to see
> that the 7th parameter is the problem.
> But I'm searching a more general way to find easily which of the parameter
> is the problem.
> Suppose you have a function with 30 parameters with mixed sort of types.
> They only way I know right now is to compare the position, name and type
> one parameter after the other until I found the one that do not match.
> A sort of brute force.
> Is there any better way to do that?
>
>>
>>
To what end?

In most cases you already know precisely which function you are trying to
execute. Comparing that single function against your call site and
figuring out what is wrong is fairly simple debugging work.

I don't see any good way to say: "given this function signature, and the
fact it cannot be found, what are the next closest function signatures that
are present".

David J.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Christophe Pettus 2023-01-16 17:57:56 Re: No function matches the given name and argument types.
Previous Message Pavel Stehule 2023-01-16 17:49:49 Re: No function matches the given name and argument types.