Skip to content

Commit 17df2a8

Browse files
committed
doc: Clarify some wording in PL/pgSQL about transactions
Some text was still claiming that committing transactions was not possible in PL/pgSQL.
1 parent e0dc839 commit 17df2a8

File tree

1 file changed

+3
-4
lines changed

1 file changed

+3
-4
lines changed

doc/src/sgml/plpgsql.sgml

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -305,10 +305,9 @@ $$ LANGUAGE plpgsql;
305305
for transaction
306306
control. <application>PL/pgSQL</application>'s <command>BEGIN</command>/<command>END</command>
307307
are only for grouping; they do not start or end a transaction.
308-
Functions are always executed within a transaction
309-
established by an outer query &mdash; they cannot start or commit that
310-
transaction, since there would be no context for them to execute in.
311-
However, a block containing an <literal>EXCEPTION</literal> clause effectively
308+
See <xref linkend="plpgsql-transactions"/> for information on managing
309+
transactions in <application>PL/pgSQL</application>.
310+
Also, a block containing an <literal>EXCEPTION</literal> clause effectively
312311
forms a subtransaction that can be rolled back without affecting the
313312
outer transaction. For more about that see <xref
314313
linkend="plpgsql-error-trapping"/>.

0 commit comments

Comments
 (0)
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy