postgres.git / summary / log / commit / refs

commit    7ceb6fb84c8cfd49c5ba92dda1c1669ba8fa687f
Author:   Peter Eisentraut <peter_e@gmx.net>
Date:     Wed Aug 22 13:42:22 2018 +0000
First released in: 12.0, 11.0

    doc: Clarify some wording in PL/pgSQL about transactions
    
    Some text was still claiming that committing transactions was not
    possible in PL/pgSQL.


 doc/src/sgml/plpgsql.sgml | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/doc/src/sgml/plpgsql.sgml b/doc/src/sgml/plpgsql.sgml
index d39a38e39d1..4344ceadbe4 100644
--- a/doc/src/sgml/plpgsql.sgml
+++ b/doc/src/sgml/plpgsql.sgml
@@ -305,10 +305,9 @@ $$ LANGUAGE plpgsql;
      for transaction
      control.  <application>PL/pgSQL</application>'s <command>BEGIN</command>/<command>END</command>
      are only for grouping; they do not start or end a transaction.
-     Functions are always executed within a transaction
-     established by an outer query &mdash; they cannot start or commit that
-     transaction, since there would be no context for them to execute in.
-     However, a block containing an <literal>EXCEPTION</literal> clause effectively
+     See <xref linkend="plpgsql-transactions"/> for information on managing
+     transactions in <application>PL/pgSQL</application>.
+     Also, a block containing an <literal>EXCEPTION</literal> clause effectively
      forms a subtransaction that can be rolled back without affecting the
      outer transaction.  For more about that see <xref
      linkend="plpgsql-error-trapping"/>.


[parent: 0a63f996e018]