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 1nyjWs-0001Mg-Vr
	for pgsql-docs@arkaria.postgresql.org; Wed, 08 Jun 2022 00:26:34 +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 1nyjWr-0005Ub-Ck
	for pgsql-docs@arkaria.postgresql.org; Wed, 08 Jun 2022 00:26:33 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <bruce@momjian.us>)
	id 1nyjWr-0005US-5I
	for pgsql-docs@lists.postgresql.org; Wed, 08 Jun 2022 00:26:33 +0000
Received: from momjian.us ([72.94.173.45])
	by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <bruce@momjian.us>)
	id 1nyjWo-0007qO-N1
	for pgsql-docs@lists.postgresql.org; Wed, 08 Jun 2022 00:26:32 +0000
Received: from bruce by momjian.us with local (Exim 4.94.2)
	(envelope-from <bruce@momjian.us>)
	id 1nyjWj-000zCY-9v; Tue, 07 Jun 2022 20:26:25 -0400
Date: Tue, 7 Jun 2022 20:26:25 -0400
From: Bruce Momjian <bruce@momjian.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: "David G. Johnston" <david.g.johnston@gmail.com>,
	Laurenz Albe <laurenz.albe@cybertec.at>, akhilhello@gmail.com,
	Pg Docs <pgsql-docs@lists.postgresql.org>
Subject: Re: correction
Message-ID: <Yp/ssfs+kBV6krjR@momjian.us>
References: <165222922369.669.10475917322916060899@wrigleys.postgresql.org>
 <d55888fe31c51c0743abe1f55dcf213633ceb30d.camel@cybertec.at>
 <Yn7BMql7NFkQLAdc@momjian.us>
 <179f4ffe247c3d6c0938217ef85948bcebb97bdb.camel@cybertec.at>
 <Yp++HQ6s6xomcCx8@momjian.us>
 <CAKFQuwZdugdJhZHkX=NJRS=DbJW8i+Px4HcvCiYVusoohiGJig@mail.gmail.com>
 <Yp/keGF4wzuvULNO@momjian.us>
 <1436965.1654646416@sss.pgh.pa.us>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="hYoSmOqe3q3nJQCk"
Content-Disposition: inline
In-Reply-To: <1436965.1654646416@sss.pgh.pa.us>
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>
Archived-At: 
 <https://www.postgresql.org/message-id/Yp/ssfs%2BkBV6krjR%40momjian.us>
Precedence: bulk


--hYoSmOqe3q3nJQCk
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Tue, Jun  7, 2022 at 08:00:16PM -0400, Tom Lane wrote:
> Bruce Momjian <bruce@momjian.us> writes:
> > +    <emphasis>not</enphasis> occur at certain isolation levels;  higher
> 
> The docs toolchain is not gonna like that.

You are correct.  I should have tested, updated patch attached.

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

  Indecision is a decision.  Inaction is an action.  Mark Batterson


--hYoSmOqe3q3nJQCk
Content-Type: text/x-diff; charset=us-ascii
Content-Disposition: attachment; filename="strict.diff"

diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml
index c7e402765f..3df4cda716 100644
--- a/doc/src/sgml/high-availability.sgml
+++ b/doc/src/sgml/high-availability.sgml
@@ -2194,7 +2194,7 @@ HINT:  You can then restart the server after making the necessary configuration
     Currently, temporary table creation is not allowed during read-only
     transactions, so in some cases existing scripts will not run correctly.
     This restriction might be relaxed in a later release. This is
-    both an SQL Standard compliance issue and a technical issue.
+    both an SQL standard compliance issue and a technical issue.
    </para>
 
    <para>
diff --git a/doc/src/sgml/mvcc.sgml b/doc/src/sgml/mvcc.sgml
index 341fea524a..c9c4f943c9 100644
--- a/doc/src/sgml/mvcc.sgml
+++ b/doc/src/sgml/mvcc.sgml
@@ -277,9 +277,10 @@
 
    <para>
     The table also shows that PostgreSQL's Repeatable Read implementation
-    does not allow phantom reads.  Stricter behavior is permitted by the
-    SQL standard: the four isolation levels only define which phenomena
-    must not happen, not which phenomena <emphasis>must</emphasis> happen.
+    does not allow phantom reads.  This is acceptable under the SQL
+    standard because the standard specifies which anomalies must
+    <emphasis>not</emphasis> occur at certain isolation levels;  higher
+    guarantees are acceptable.
     The behavior of the available isolation levels is detailed in the
     following subsections.
    </para>

--hYoSmOqe3q3nJQCk--