| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Robin Abbi <robin(dot)abbi(at)downley(dot)net> |
| Cc: | Dave Cramer <davecramer(at)postgres(dot)rocks>, pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Procedures |
| Date: | 2020-08-06 22:10:52 |
| Message-ID: | 20200806221052.GA23547@momjian.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Thu, Aug 6, 2020 at 02:30:55PM +0100, Robin Abbi wrote:
> PostgreSQL went as far as release 10 without procedures.
> Some third party resources written before 11 loosely conflate procedures with
> functions.
> Some third party resources written before 11 accurately state PostgreSQL has
> functions but not procedures.
> Referring to the PostgreSQL docs for 11 on, procedures have been added.
>
> For someone like me, coming to the subject without much of a hinterland other
> than googling around, it seemed clear that there was a motivating case that
> caused Procedures to be added to PostgreSQL, but I was not sufficiently
> familiar with the domain to be able to readily intuit what it might have been.
>
> For example, Procedures say they have no return value, yet Functions can return
> void. Not the same I agree, but I wouldn't be aware in which circumstances it
> mattered.
>
> For me, perhaps the most useful thing would have been a small example
> highlighting the essential thing(s) that procedures can do that functions could
> not.
Agreed, this doc area needs help.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EnterpriseDB https://enterprisedb.com
The usefulness of a cup is in its emptiness, Bruce Lee
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jürgen Purtz | 2020-08-07 15:46:45 | Re: obsolete indexing method "rtree" |
| Previous Message | Robin Abbi | 2020-08-06 13:30:55 | Re: Procedures |