summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2020-10-26 22:38:11 -0400
committerBruce Momjian <bruce@momjian.us>2020-10-26 22:38:11 -0400
commit58947869528dad323196bf79bd0b08c52c5e33c5 (patch)
treeb8d5d352689300288ae830a53317bd7cc15b40e3
parenteb435768889467fb7e4bb84321f4347e25377e5a (diff)
doc: simplify wording of function error affects
Reported-by: bob.henkel@gmail.com Discussion: https://postgr.es/m/160324449781.693.8298142858847611071@wrigleys.postgresql.org Backpatch-through: 9.5
-rw-r--r--doc/src/sgml/plpgsql.sgml4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/src/sgml/plpgsql.sgml b/doc/src/sgml/plpgsql.sgml
index 58699eb7a13..d3660407002 100644
--- a/doc/src/sgml/plpgsql.sgml
+++ b/doc/src/sgml/plpgsql.sgml
@@ -2573,8 +2573,8 @@ NOTICE: row = {10,11,12}
<para>
By default, any error occurring in a <application>PL/pgSQL</>
- function aborts execution of the function, and indeed of the
- surrounding transaction as well. You can trap errors and recover
+ function aborts execution of the function and the
+ surrounding transaction. You can trap errors and recover
from them by using a <command>BEGIN</> block with an
<literal>EXCEPTION</> clause. The syntax is an extension of the
normal syntax for a <command>BEGIN</> block: