diff options
| author | Peter Eisentraut <peter_e@gmx.net> | 2018-08-22 15:42:22 +0200 |
|---|---|---|
| committer | Peter Eisentraut <peter_e@gmx.net> | 2018-08-22 15:42:22 +0200 |
| commit | 7ceb6fb84c8cfd49c5ba92dda1c1669ba8fa687f (patch) | |
| tree | 30a559afa2f5a46763b732a40c2096a22561434c | |
| parent | 0a63f996e018ac508c858e87fa39cc254a5db49f (diff) | |
| download | postgresql-7ceb6fb84c8cfd49c5ba92dda1c1669ba8fa687f.tar.gz postgresql-7ceb6fb84c8cfd49c5ba92dda1c1669ba8fa687f.zip | |
doc: Clarify some wording in PL/pgSQL about transactions
Some text was still claiming that committing transactions was not
possible in PL/pgSQL.
| -rw-r--r-- | doc/src/sgml/plpgsql.sgml | 7 |
1 files 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 — 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"/>. |