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
This commit is contained in:
parent
3a1f6a2581
commit
785affc1d6
@ -84,8 +84,11 @@
|
|||||||
A procedure is a database object similar to a function. The difference is
|
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
|
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
|
declaration. While a function is called as part of a query or DML
|
||||||
command, a procedure is called explicitly using
|
command, a procedure is called in isolation using
|
||||||
the <xref linkend="sql-call"/> statement.
|
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>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
|
Loading…
x
Reference in New Issue
Block a user