Message-ID: <d55888fe31c51c0743abe1f55dcf213633ceb30d.camel@cybertec.at>
Subject: Re: correction
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: akhilhello@gmail.com, pgsql-docs@lists.postgresql.org
Date: Wed, 11 May 2022 12:36:11 +0200
In-Reply-To: <165222922369.669.10475917322916060899@wrigleys.postgresql.org>
References: <165222922369.669.10475917322916060899@wrigleys.postgresql.org>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.42.4 (3.42.4-2.fc35) 
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/d55888fe31c51c0743abe1f55dcf213633ceb30d.camel%40cybertec.at>
Precedence: bulk

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.

Yours,
Laurenz Albe