Re: CALL and named parameters - Mailing list pgsql-general

From Tom Lane
Subject Re: CALL and named parameters
Date
Msg-id 1635992.1754609605@sss.pgh.pa.us
Whole thread Raw
In response to Re: CALL and named parameters  (Christoph Moench-Tegeder <cmt@burggraben.net>)
Responses Re: CALL and named parameters
List pgsql-general
Christoph Moench-Tegeder <cmt@burggraben.net> writes:
> ## Dominique Devienne (ddevienne@gmail.com):
>> dd_v185=> call "Epos-DBA".db_grant_connect_to(grantee_role => 'dd_joe');
>> ERROR:  procedure Epos-DBA.db_grant_connect_to(grantee_role =>
>> unknown) does not exist
>> LINE 1: call "Epos-DBA".db_grant_connect_to(grantee_role => 'dd_joe'...

> There's the problem: "unknown" type - consider that string there as
> "too flexible", it can be coerced into too many types, so the error
> says "unknown".

No, the issue is that the procedure's named parameter is not named
"grantee_role" but something else.  We'd have coerced the unknown
parameter just fine, except that we never considered this procedure
as a valid match at all.

            regards, tom lane



pgsql-general by date:

Previous
From: Christoph Moench-Tegeder
Date:
Subject: Re: CALL and named parameters
Next
From: Charles Qi
Date:
Subject: Re: When UPDATE a row in a table with BEFORE ROW UPDATE trigger, the XMAX of new tuple is set to current XID