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 1npc1C-0006bN-IG
	for pgsql-docs@arkaria.postgresql.org; Fri, 13 May 2022 20:36:10 +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 1npc1B-00031w-Dz
	for pgsql-docs@arkaria.postgresql.org; Fri, 13 May 2022 20:36:09 +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 1npc1B-00031n-6x
	for pgsql-docs@lists.postgresql.org; Fri, 13 May 2022 20:36:09 +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 1npc18-0003Q9-O6
	for pgsql-docs@lists.postgresql.org; Fri, 13 May 2022 20:36:08 +0000
Received: from bruce by momjian.us with local (Exim 4.94.2)
	(envelope-from <bruce@momjian.us>)
	id 1npc14-00HEsK-Bk; Fri, 13 May 2022 16:36:02 -0400
Date: Fri, 13 May 2022 16:36:02 -0400
From: Bruce Momjian <bruce@momjian.us>
To: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: akhilhello@gmail.com, pgsql-docs@lists.postgresql.org
Subject: Re: correction
Message-ID: <Yn7BMql7NFkQLAdc@momjian.us>
References: <165222922369.669.10475917322916060899@wrigleys.postgresql.org>
 <d55888fe31c51c0743abe1f55dcf213633ceb30d.camel@cybertec.at>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="lmCI8o1hsIYpN1dm"
Content-Disposition: inline
In-Reply-To: <d55888fe31c51c0743abe1f55dcf213633ceb30d.camel@cybertec.at>
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/Yn7BMql7NFkQLAdc%40momjian.us>
Precedence: bulk


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

On Wed, May 11, 2022 at 12:36:11PM +0200, Laurenz Albe wrote:
> On Wed, 2022-05-11 at 00:33 +0000, PG Doc comments form wrote:
> > The following documentation comment has been logged on the website:
> > 
> > Page: https://www.postgresql.org/docs/14/transaction-iso.html
> > Description:
> > 
> > in this page: https://www.postgresql.org/docs/14/transaction-iso.html
> > 
> > under the Table 13.1 section, if we search for "phantom reads. Stricter
> > behavior is permitted by the SQL standard", do we mean "Looser behaviour"?
> 
> What is meant is "The SQL standard allows an implementation to implement
> stricter behavior than required by the standard; it only defines the things
> that are *not* allowed to happen at a certain isolation level.  So it is for
> example fine for PostgreSQL not to allow dirty reads in READ UNCOMMITTED
> isolation level."
> 
> Perhaps this could be rewritten to be clearer; it is indeed easy to
> misunderstand that sentence.

How is this attached patch's wording?

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

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


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

diff --git a/doc/src/sgml/mvcc.sgml b/doc/src/sgml/mvcc.sgml
index 341fea524a..244694b07f 100644
--- a/doc/src/sgml/mvcc.sgml
+++ b/doc/src/sgml/mvcc.sgml
@@ -277,8 +277,8 @@
 
    <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
+    does not allow phantom reads.  The SQL standard allows more restrictive
+    behavior:  the four isolation levels only define which phenomena
     must not happen, not which phenomena <emphasis>must</emphasis> happen.
     The behavior of the available isolation levels is detailed in the
     following subsections.

--lmCI8o1hsIYpN1dm--