]> granicus.if.org Git - postgresql/commitdiff
doc: Clarify some wording in PL/pgSQL about transactions
authorPeter Eisentraut <peter_e@gmx.net>
Wed, 22 Aug 2018 13:42:22 +0000 (15:42 +0200)
committerPeter Eisentraut <peter_e@gmx.net>
Wed, 22 Aug 2018 13:43:07 +0000 (15:43 +0200)
Some text was still claiming that committing transactions was not
possible in PL/pgSQL.

doc/src/sgml/plpgsql.sgml

index 6b19f18dd897a509f4764ec85fef054d0d880ee6..e80b57bb3d0a05afcb19496487c04d4aa8d503cf 100644 (file)
@@ -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"/>.