From 3b897642314fdb31a202ba7749eb45a5f439e79e Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Mon, 26 Oct 2020 22:38:11 -0400
Subject: [PATCH] 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
---
doc/src/sgml/plpgsql.sgml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/src/sgml/plpgsql.sgml b/doc/src/sgml/plpgsql.sgml
index 93dacabc16..5e75c47d68 100644
--- a/doc/src/sgml/plpgsql.sgml
+++ b/doc/src/sgml/plpgsql.sgml
@@ -2615,8 +2615,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: