| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Christoph Moench-Tegeder <cmt(at)burggraben(dot)net> |
| Cc: | Dominique Devienne <ddevienne(at)gmail(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: CALL and named parameters |
| Date: | 2025-08-07 23:33:25 |
| Message-ID: | 1635992.1754609605@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Christoph Moench-Tegeder <cmt(at)burggraben(dot)net> writes:
> ## Dominique Devienne (ddevienne(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Charles Qi | 2025-08-08 01:20:00 | Re: When UPDATE a row in a table with BEFORE ROW UPDATE trigger, the XMAX of new tuple is set to current XID |
| Previous Message | Christoph Moench-Tegeder | 2025-08-07 23:14:07 | Re: CALL and named parameters |