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
commit98529445a360144f71092a9377cb5fc3e2d634e2 (patch)
treeafae9d2e85ad6f9ed250183e8984fe3b0993b651
parent758b45e83b50b08a0bca03a9b5610a27ed7c7b09 (diff)
downloadpostgresql-98529445a360144f71092a9377cb5fc3e2d634e2.tar.gz
postgresql-98529445a360144f71092a9377cb5fc3e2d634e2.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 91e8973c421..12c42e3fd54 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: