Skip to content

Commit 243a3b9

Browse files
committed
doc: clarify the useful features of procedures
This was not clearly documented when procedures were added in PG 11. Reported-by: Robin Abbi Discussion: https://postgr.es/m/CAGmg_NX327KKVuJmbWZD=pGutYFxzZjX1rU+3ji8UuX=8ONn9Q@mail.gmail.com Backpatch-through: 11
1 parent 3a788db commit 243a3b9

File tree

1 file changed

+5
-2
lines changed

1 file changed

+5
-2
lines changed

doc/src/sgml/xfunc.sgml

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -84,8 +84,11 @@
8484
A procedure is a database object similar to a function. The difference is
8585
that a procedure does not return a value, so there is no return type
8686
declaration. While a function is called as part of a query or DML
87-
command, a procedure is called explicitly using
88-
the <xref linkend="sql-call"/> statement.
87+
command, a procedure is called in isolation using
88+
the <xref linkend="sql-call"/> command. If the CALL command is not
89+
part of an explicit transaction, a procedure in many server-side
90+
languages can commit, rollback, and begin new transactions during
91+
its execution, which is not possible in functions.
8992
</para>
9093

9194
<para>

0 commit comments

Comments
 (0)