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-22 17:08:54 |
Message-ID: | 20200822170854.GE26781@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On Sat, Aug 22, 2020 at 12:05:24PM +0100, Robin Abbi wrote:
> On Fri, 21 Aug 2020 at 23:52, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>
> I developed the attached patach for this. Is this sufficient?
>
>
> Would it be appropriate to consider including some language with a similar
> information content to this
>
> " ... prior to PostgreSQL 11, these functions were unable to manage their
> own transactions. PostgreSQL 11 adds SQL procedures that can perform full
> transaction management within the body of a function, enabling developers
> to create more advanced server-side applications, such as ones involving
> incremental bulk data loading."
>
> from here https://www.postgresql.org/about/news/1894/ .
No, we would only mention it if there some kind of incompatibility here.
We always have to balance adding text with making the text longer and
harder to read.
--
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 | Bruce Momjian | 2020-08-22 17:14:47 | Re: Procedures |
Previous Message | Bruce Momjian | 2020-08-22 16:55:34 | Re: Document "59.2. Built-in Operator Classes" have a clerical error? |