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

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Mark <nvpostgres(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Debugging --- ERROR: function does not exist
Date: 2026-10-25 19:55:53
Message-ID: 96b548fc-65b8-413a-bdd3-345f94f029c4@aklaver.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 10/25/26 11:00 AM, Tom Lane wrote:
> Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> writes:
>> On 10/25/26 8:34 AM, Mark wrote:
>>      "To call a function with OUT parameters, omit the output
>>      parameter(s) in
>>      the function call: ..."
>
> That's what you do in SELECT, but in CALL you write all six
> arguments (and the ones corresponding to OUT parameters
> have to be variables).

From here:

https://www.postgresql.org/docs/current/sql-call.html

"CALL executes a procedure."

"To call a function (not a procedure), use SELECT instead."

So is the problem down to the OP defining a function not a procedure and
therefore not being able to use CALL to get at the OUT parameters?

>
> 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 Tom Lane 2026-10-25 20:19:51 Re: Debugging --- ERROR: function does not exist
Previous Message Laurenz Albe 2026-10-25 19:04:51 Re: PostgreSQL 17: protecting role attributes between verification and COMMIT