aboutsummaryrefslogtreecommitdiff
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
commit209e8e4c8747434a70f0add141d8ef26252b549c (patch)
treefbc0a6ed9d4239a8039b399e44156c2159c06e8f
parentbaad9adfa988f34996e0ce377e7e68da70df975e (diff)
downloadpostgresql-209e8e4c8747434a70f0add141d8ef26252b549c.tar.gz
postgresql-209e8e4c8747434a70f0add141d8ef26252b549c.zip
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 e4addcc312c..3e0d7cfa01b 100644
--- a/doc/src/sgml/plpgsql.sgml
+++ b/doc/src/sgml/plpgsql.sgml
@@ -2607,8 +2607,8 @@ NOTICE: row = {10,11,12}
<para>
By default, any error occurring in a <application>PL/pgSQL</application>
- 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</command> block with an
<literal>EXCEPTION</literal> clause. The syntax is an extension of the
normal syntax for a <command>BEGIN</command> block: