Horton

Re: CALL versus procedures with output-only arguments

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Cc: Robert Haas <robertmhaas@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2021-05-31T20:25:19Z
Lists: pgsql-hackers 
I wrote:
> Peter Eisentraut <peter.eisentraut@enterprisedb.com> writes:
>> I don't see that.

> It's under CREATE PROCEDURE.  11.60 <SQL-invoked routine> SR 20 says

Oh... just noticed something else relevant to this discussion: SR 13
in the same section saith

  13) If R is an SQL-invoked function, then no <SQL parameter declaration>
  in NPL shall contain a <parameter mode>.

In other words, the spec does not have OUT or INOUT parameters for
functions.  So, again, their notion of what is sufficient to identify
a routine is based on a very different model than what we are using.  

			regards, tom lane

Commits

  1. Reconsider the handling of procedure OUT parameters.