Re: CALL versus procedures with output-only arguments - Mailing list pgsql-hackers

From Laurenz Albe
Subject Re: CALL versus procedures with output-only arguments
Date
Msg-id efe55e8d2d83c3761e46789fa86cdc4b013a7ba6.camel@cybertec.at
Whole thread Raw
In response to Re: CALL versus procedures with output-only arguments  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: CALL versus procedures with output-only arguments  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-hackers
On Mon, 2021-05-31 at 15:55 -0400, Tom Lane wrote:
> > If I have two procedures
> > p1(IN int, IN int, OUT int, OUT int)
> > p1(OUT int, OUT int)
> > then a DROP, or ALTER, or GRANT, etc. on p1(int, int) should operate on 
> > the second one in a spec-compliant implementation, but you propose to 
> > have it operate on the first one.  That kind of discrepancy would be 
> > really bad to have.
> 
> We already have that situation for functions.  I think having procedures
> work differently from functions is much worse than your complaint here;
> and I do not see why being spec-compliant for one case when we are not
> for the other is a good situation to be in.

+1

Yours,
Laurenz Albe




pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: be-secure-gssapi.c and auth.c with setenv() not compatible on Windows
Next
From: Michael Paquier
Date:
Subject: Re: Alias collision in `refresh materialized view concurrently`