Re: correction

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: akhilhello(at)gmail(dot)com, pgsql-docs(at)lists(dot)postgresql(dot)org
Subject: Re: correction
Date: 2022-05-11 10:36:11
Message-ID: d55888fe31c51c0743abe1f55dcf213633ceb30d.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

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

In response to

  • correction at 2022-05-11 00:33:43 from PG Doc comments form

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message PG Doc comments form 2022-05-11 13:45:20 SET TRANSACTION SNAPSHOT sounds like replicated environment but isn't
Previous Message PG Doc comments form 2022-05-11 00:33:43 correction