From: | Dave Cramer <davecramer(at)postgres(dot)rocks> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | robin(dot)abbi(at)downley(dot)net, pgsql-docs(at)lists(dot)postgresql(dot)org |
Subject: | Re: Procedures |
Date: | 2020-08-06 10:32:13 |
Message-ID: | CADK3HH+cyx-aFnf8Tzra2qtBwD+e-k-cpnrjXhX9G9_-MKJj4A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On Wed, 5 Aug 2020 at 20:18, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> On Tue, Aug 4, 2020 at 10:33:49AM +0000, PG Doc comments form wrote:
> > The following documentation comment has been logged on the website:
> >
> > Page: https://www.postgresql.org/docs/11/sql-createprocedure.html
> > Description:
> >
> > The information on procedures could helpfully include that the feature is
> > new from PostgreSQL 11 and give an explanation of how it differs from
> > functions. I found the information I needed here
> > https://dba.stackexchange.com/a/262662, but I think it would really
> benefit
> > others if the information was provided in the official documentation.
>
> We don't normally mention what release added a features. However, I do
> see your problem with finding that procedures can issue transaction
> control statements. I see this for procedures:
>
> https://www.postgresql.org/docs/12/xproc.html
>
> but that has no mention of transactions, just a mention of using CALL,
> then this pl/pgSQL section about transaction control mentions CALL:
>
> https://www.postgresql.org/docs/12/plpgsql-transactions.html
>
> Is this what you think needs improving?
>
> Neither of those places mention that procedures cannot be called inside a
transaction.
So ya I think there there is some room for improvement
Dave Cramer
www.postgres.rocks
From | Date | Subject | |
---|---|---|---|
Next Message | Robin Abbi | 2020-08-06 13:30:55 | Re: Procedures |
Previous Message | David G. Johnston | 2020-08-06 08:12:13 | Re: obsolete indexing method "rtree" |