postgres.git / summary / log / commit / refs

commit    5277f493dde7de00250d33a8ea79a5b93ee89dae
Author:   Bruce Momjian <bruce@momjian.us>
Date:     Mon Aug 31 17:20:04 2020 +0000
First released in: 14.0, 11.10, 12.5, 13.0

    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


 doc/src/sgml/xfunc.sgml | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/doc/src/sgml/xfunc.sgml b/doc/src/sgml/xfunc.sgml
index 8bf497b2bf9..04ef0a85a72 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>


[parent: 73952310bfcd]