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

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Mark <nvpostgres(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Debugging --- ERROR: function does not exist
Date: 2026-10-26 14:43:23
Message-ID: 7a75e04d-7eca-4696-9f4d-8a80adafc6ab@aklaver.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 10/26/26 3:56 AM, Mark wrote:
> Correction for anybody who reads this later:
>
> Adrian
>
> I eventually got what you were hinting at, I should INOUT to supply the
> parameters at part of the SELECT, though I feel like this is not a good
> idea unless actually required from a security perspective (though I
> acknowledge this will be a trivial difference)

Given that OUT is basically an alternate form of RETURNS why do you want
to supply the OUT values to the function/procedure SELECT/CALL in the
first place?

That would be something the function/procedure does internally using the
IN values, where IN is either explicitly stated or implied by a lack of
an IN/OUT/INOUT declaration.

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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Mark 2026-10-26 15:21:59 Re: Debugging --- ERROR: function does not exist
Previous Message Tom Lane 2026-10-26 13:47:05 Re: Debugging --- ERROR: function does not exist