doc: Clarify some wording in PL/pgSQL about transactions

Some text was still claiming that committing transactions was not
possible in PL/pgSQL.

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