postgres.git / summary / log / commit / refs

commit    a645c08838d6d4ae55ac4df57cfd91f0b9e4f812
Author:   Bruce Momjian <bruce@momjian.us>
Date:     Tue Oct 27 02:38:11 2020 +0000
First released in: 14.0, 9.5.24, 9.6.20, 10.15, 11.10, 12.5, 13.1

    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 a71a8e7e487..ad1abdd0cab 100644
--- a/doc/src/sgml/plpgsql.sgml
+++ b/doc/src/sgml/plpgsql.sgml
@@ -2632,8 +2632,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:


[parent: 4747655111b0]