Re: CALL versus procedures with output-only arguments
Andrew Dunstan <andrew@dunslane.net>
From: Andrew Dunstan <andrew@dunslane.net>
To: Tom Lane <tgl@sss.pgh.pa.us>,
Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2021-05-24T12:22:05Z
Lists: pgsql-hackers
On 5/23/21 8:01 PM, Tom Lane wrote: > I wrote: >> I think we ought to fix this so that OUT-only arguments are ignored >> when calling from SQL not plpgsql. > I'm working on a patch to make it act that way. I've got some issues > yet to fix with named arguments (which seem rather undertested BTW, > since the patch is passing check-world even though I know it will > crash instantly on cases with CALL+named-args+out-only-args). > > Before I spend too much time on it though, I wanted to mention that > it includes undoing 2453ea142's decision to include OUT arguments > in pg_proc.proargtypes for procedures (but not for any other kind of > routine). I thought that was a terrible decision and I'm very happy > to revert it, but is anyone likely to complain loudly? > > Possibly, Will take a look. IIRC we have based some other things on this. cheers andrew -- Andrew Dunstan EDB: https://www.enterprisedb.com
Commits
-
Reconsider the handling of procedure OUT parameters.
- e56bce5d4378 14.0 landed