aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2020-08-31 13:20:04 -0400
committerBruce Momjian <bruce@momjian.us>2020-08-31 13:20:04 -0400
commit785affc1d653bac43b7d4fad93f22e9e51aefcc1 (patch)
tree8bffd85b5963cdfafd1ec8bdb47c340a772edab0
parent3a1f6a2581e41ee2c724e8422675942d30a52ff7 (diff)
downloadpostgresql-785affc1d653bac43b7d4fad93f22e9e51aefcc1.tar.gz
postgresql-785affc1d653bac43b7d4fad93f22e9e51aefcc1.zip
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
-rw-r--r--doc/src/sgml/xfunc.sgml7
1 files changed, 5 insertions, 2 deletions
diff --git a/doc/src/sgml/xfunc.sgml b/doc/src/sgml/xfunc.sgml
index 6de464c6545..732d9355212 100644
--- a/doc/src/sgml/xfunc.sgml
+++ b/doc/src/sgml/xfunc.sgml
@@ -84,8 +84,11 @@
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 in many server-side
+ languages can commit, rollback, and begin new transactions during
+ its execution, which is not possible in functions.
</para>
<para>