On Fri, Aug 21, 2020 at 07:42:35PM -0700, David G. Johnston wrote:
> On Fri, Aug 21, 2020 at 3:52 PM Bruce Momjian <[email protected]> wrote:
>
>
> > Agreed, this doc area needs help.
>
> I developed the attached patach for this. Is this sufficient?
>
>
> For consistency I would change "statement" to "command" at the end of that
> paragraph .
>
> the <xref linkend="sql-call"/> command.
>
> and to contrast with "a part of" I would modify the following fragment to
> read:
>
> a procedure is called in isolation
>
> Taken together:
>
> While a function is called as part of a query or DML command, a procedure is
> called in isolation using the <xref linked="sql-call"/> command.
>
> And then swap the order of, and tweak, the transaction and isolation
> sentences:
>
> [...] the CALL command. If the CALL command is not part of an explicit
> transaction a procedure can also manage multiple transactions during its
> execution.
OK, how is this updated patch?
--
Bruce Momjian <[email protected]> https://momjian.us
EnterpriseDB https://enterprisedb.com
The usefulness of a cup is in its emptiness, Bruce Lee
diff --git a/doc/src/sgml/xfunc.sgml b/doc/src/sgml/xfunc.sgml
index 6de464c654..1fdd98d41d 100644
--- a/doc/src/sgml/xfunc.sgml
+++ b/doc/src/sgml/xfunc.sgml
@@ -84,8 +84,10 @@
A procedure is a database object similar to a function. The difference is
that a procedure does not return a value, so there is no return type
declaration. While a function is called as part of a query or DML
- command, a procedure is called explicitly using
- the <xref linkend="sql-call"/> statement.
+ command, a procedure is called in isolation using
+ the <xref linkend="sql-call"/> command. If the CALL command is not
+ part of an explicit transaction, a procedure can begin and commit
+ multiple transactions during its execution.
</para>
<para>
