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

From: Mark <nvpostgres(at)gmail(dot)com>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Debugging --- ERROR: function does not exist
Date: 2026-10-26 10:52:50
Message-ID: CAAm-KOsLrej-X68btFxGPg=NHOejFvUwcQ8_dNzhKdkHQvTmZQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Sun, Oct 25, 2026 at 8:34 PM David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:

> On Sun, Oct 25, 2026 at 4:50 AM Mark <nvpostgres(at)gmail(dot)com> wrote:
>
>> If I run \df getsSessDbKey I get:
>> Schema | Name | Result data type |
>> Argument data types
>> | Type
>>
>> --------+--------------+------------------+--------------------------------------------------------------------------------------------------------------------+------
>> public | getsessdbkey | record | isessionid text, iuser text,
>> ifunction text, OUT osessdbkey bigint, OUT osessret customtype, OUT
>> retsessdbmess text | func
>>
>
>> Any pointers into how I can find out more about this error or hints on
>> how to resolve this would be heavily appreciated?
>>
>
> Show the code you actually wrote. If you cannot do that, write similar
> code that produces the same error and show that.
>
> For that function you'd probably write something like:
>
> select osessdbkey, osessret, retsessdbmess
> into var1, var2, var3
> from getsSessDbKey(isessionid, iuser, ifunction);
>
> to execute the function and capture the three output fields.
>
> David J.
>
> P.S. As for the 'memory locations' comment - that seems like something you
> misunderstood and thus acted upon unnecessarily.
>
>
> Thanks David for your input

I got it working from the comments by Tom and Adrian, I could not use the
example you provided due to the customType not being a scalar (it is a
number, text field, and a few JSONs)

Thanks for the comment on memory locations, yes that seems to be a red
herring, do you have any thing you can point to on memory locations (in
this context) that I can read, or it is just not necessary to consider
overall

Mark

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Mark 2026-10-26 10:56:31 Re: Debugging --- ERROR: function does not exist
Previous Message Christophe Pettus 2026-10-26 10:50:52 Re: PostgreSQL 17 — Native Password Policy Support