From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [HACKERS] SQL procedures |
Date: | 2018-01-02 17:19:50 |
Message-ID: | CAFj8pRC3yfg0tYikCyooW8KvxorWrFOnNDcc-ZFsA4fSWMD_Gg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2018-01-02 17:47 GMT+01:00 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> > I agree that we need this, but using prorettype = InvalidOid to do it
> > might not be the best way, because it only works for procedures that
> > don't return anything. If a procedure could return, say, an integer,
>
> Good point, because that is possible in some other systems, and so
> somebody is going to ask for it at some point.
>
> > Anyway, I think it would be better to invent an explicit way to
> > represent whether something is a procedure rather than relying on
> > overloading prorettype to tell us.
>
> +1 --- seems like a new bool column is the thing. Or may we should merge
> "proisprocedure" with proisagg and proiswindow into an enum prokind?
> Although that would break some existing client-side code.
>
+1
Pavel
> PS: I still strongly disagree with allowing prorettype to be zero.
>
> regards, tom lane
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Marco Nenciarini | 2018-01-02 18:11:11 | Re: [PATCH] Logical decoding of TRUNCATE |
Previous Message | Stephen Frost | 2018-01-02 17:13:02 | Re: Add default role 'pg_access_server_files' |