Re: Debugging --- ERROR: function does not exist

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Mark <nvpostgres(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Debugging --- ERROR: function does not exist
Date: 2026-10-25 14:42:55
Message-ID: a34cf760-8d6c-49bb-be80-43c5b4a499ee@aklaver.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 10/25/26 6:26 AM, Mark wrote:
> Thanks for the input Tom
>
> 1) SHOW search_path; -- produces the following and the function was in
> the public schema (and both created by the same user)
>
>   search_path
> -----------------
> "$user", public
>
> 2) I was calling it with:
> SELECTgetSessDbKey (jSessionId, jUser, 'functionName'::text, vSessDbKey,
> vSessRet, vGetSessDbKeyMess);

This is not the same as:

SELECT getSessDbKey (iSessionId => '1234'::text, iUser => 'cmd
test'::text, iFunction => 'cmd test'::text);

Note 3 parameters vs 6 in the 2).

And from here:

https://www.postgresql.org/docs/current/plpgsql-declarations.html#PLPGSQL-DECLARATION-PARAMETERS

"To call a function with OUT parameters, omit the output parameter(s) in
the function call: ..."

>
> I just tried to user CALL and the HINT was to use SELECT
>
> Mark
>
> On Sun, Oct 25, 2026 at 1:00 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us
> <mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us>> wrote:
>
> Mark <nvpostgres(at)gmail(dot)com <mailto:nvpostgres(at)gmail(dot)com>> writes:
> > I am getting the following error which has been driving me crazy:
> > ERROR:  function getsessdbkey(text, text, text, bigint,
> customType, text)
> > does not exist
>
> (1) search_path problem, perhaps?
> (2) are you using a CALL statement to call it?
>
>                         regards, tom lane
>

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2026-10-25 14:54:21 Re: Debugging --- ERROR: function does not exist
Previous Message Dustin Sanza 2026-10-25 14:04:08 Re: PostgreSQL 17: protecting role attributes between verification and COMMIT