Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <pgsql-docs-owner+archive@lists.postgresql.org>)
	id 1kXEvi-0005xB-Q1
	for pgsql-docs@arkaria.postgresql.org; Tue, 27 Oct 2020 02:41:46 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-docs-owner+archive@lists.postgresql.org>)
	id 1kXEvh-0005iM-Oa
	for pgsql-docs@arkaria.postgresql.org; Tue, 27 Oct 2020 02:41:45 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <bruce@momjian.us>)
	id 1kXEsd-0002ai-LT
	for pgsql-docs@lists.postgresql.org; Tue, 27 Oct 2020 02:38:35 +0000
Received: from momjian.us ([72.94.173.45])
	by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <bruce@momjian.us>)
	id 1kXEsb-0003BC-FI
	for pgsql-docs@lists.postgresql.org; Tue, 27 Oct 2020 02:38:34 +0000
Received: from bruce by momjian.us with local (Exim 4.92)
	(envelope-from <bruce@momjian.us>)
	id 1kXEsa-0006Si-EN; Mon, 26 Oct 2020 22:38:32 -0400
Date: Mon, 26 Oct 2020 22:38:32 -0400
From: Bruce Momjian <bruce@momjian.us>
To: "David G. Johnston" <david.g.johnston@gmail.com>
Cc: bob.henkel@gmail.com, Pg Docs <pgsql-docs@lists.postgresql.org>
Subject: Re: Word fix
Message-ID: <20201027023832.GF4951@momjian.us>
References: <160324449781.693.8298142858847611071@wrigleys.postgresql.org>
 <CAKFQuwbLb16kwO_n62fu+=u-OHN8rhaAxZog3VAq-HNf4Hx8jw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="ZoaI/ZTpAVc4A5k6"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: 
 <CAKFQuwbLb16kwO_n62fu+=u-OHN8rhaAxZog3VAq-HNf4Hx8jw@mail.gmail.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
List-Id: <pgsql-docs.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-docs@lists.postgresql.org>
List-Owner: <mailto:pgsql-docs-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-docs>
Precedence: bulk


--ZoaI/ZTpAVc4A5k6
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit

On Wed, Oct 21, 2020 at 06:49:37AM -0700, David G. Johnston wrote:
> On Wed, Oct 21, 2020 at 1:14 AM PG Doc comments form <noreply@postgresql.org>
> wrote:
> 
>     The following documentation comment has been logged on the website:
> 
>     Page: https://www.postgresql.org/docs/13/plpgsql-control-structures.html
>     Description:
> 
>     Search for the word indeed found here
>     https://www.postgresql.org/docs/13/plpgsql-control-structures.html#
>     PLPGSQL-STATEMENTS-RETURNING-PROCEDURE
>     and replace with inside.
> 
> 
> Specifically:
> 
> "By default, any error occurring in a PL/pgSQL function aborts execution of the
> function, and indeed of the surrounding transaction as well."
> 
> Replacing it with "inside" is not an improvement.  Removing "indeed of" is
> probably sufficient.

Fixed in all branches with the attached patch.

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EnterpriseDB                             https://enterprisedb.com

  The usefulness of a cup is in its emptiness, Bruce Lee


--ZoaI/ZTpAVc4A5k6
Content-Type: text/x-diff; charset=us-ascii
Content-Disposition: attachment; filename="plpgsql.diff"

diff --git a/doc/src/sgml/plpgsql.sgml b/doc/src/sgml/plpgsql.sgml
index 94a3b36458..9ec168b0c4 100644
--- a/doc/src/sgml/plpgsql.sgml
+++ b/doc/src/sgml/plpgsql.sgml
@@ -2670,8 +2670,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:

--ZoaI/ZTpAVc4A5k6--