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: "David G. Johnston" <david.g.johnston@gmail.com>
Cc: Laurenz Albe <laurenz.albe@cybertec.at>, Peter Eisentraut <peter.eisentraut@enterprisedb.com>, Robert Haas <robertmhaas@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2021-06-01T17:46:05Z
Lists: pgsql-hackers 
"David G. Johnston" <david.g.johnston@gmail.com> writes:
> When this discussion concludes a review of the compatibility sections of
> the create/drop “routine” reference pages would be appreciated.

Good idea, whichever answer we settle on.  But it's notable that
the existing text gives no hint that the rules are different
for functions and procedures.  That will need work if we leave
the code as it stands.

			regards, tom lane

Commits

  1. Reconsider the handling of procedure OUT parameters.