Re: correction

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
Cc: akhilhello(at)gmail(dot)com, pgsql-docs(at)lists(dot)postgresql(dot)org
Subject: Re: correction
Date: 2022-05-13 20:36:02
Message-ID: Yn7BMql7NFkQLAdc@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

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(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com

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

Attachment Content-Type Size
strict.diff text/x-diff 732 bytes

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Laurenz Albe 2022-05-13 21:49:09 Re: correction
Previous Message Bruce Momjian 2022-05-13 18:41:39 Re: Documentation Suggestion