Date: Tue, 7 Jun 2022 19:51:20 -0400
From: Bruce Momjian <bruce@momjian.us>
To: "David G. Johnston" <david.g.johnston@gmail.com>
Cc: Laurenz Albe <laurenz.albe@cybertec.at>, akhilhello@gmail.com,
	Pg Docs <pgsql-docs@lists.postgresql.org>
Subject: Re: correction
Message-ID: <Yp/keGF4wzuvULNO@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>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="n1vyPUNquHhjSIPA"
Content-Disposition: inline
In-Reply-To: 
 <CAKFQuwZdugdJhZHkX=NJRS=DbJW8i+Px4HcvCiYVusoohiGJig@mail.gmail.com>
Archived-At: 
 <https://www.postgresql.org/message-id/Yp/keGF4wzuvULNO%40momjian.us>
Precedence: bulk


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

On Tue, Jun  7, 2022 at 02:40:41PM -0700, David G. Johnston wrote:
> On Tue, Jun 7, 2022 at 2:07 PM Bruce Momjian <bruce@momjian.us> wrote:
> 
> 
> 
>     How is this, attached?
> 
> 
> 
> Works for me.
> 
> Capital "S" in Standard as a proper name? (mind grepping this to see how
> consistent we are one way or the other, I'm not setup for that at the moment)

Well, that's a good question.  Seems we use "SQL standard", and I found
one place where we capitalize "Standard", so fixed too in this patch.

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

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


--n1vyPUNquHhjSIPA
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..112d6ce7a8 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</enphasis> occur at certain isolation levels;  higher
+    guarantees are acceptable.
     The behavior of the available isolation levels is detailed in the
     following subsections.
    </para>

--n1vyPUNquHhjSIPA--