From: Bruce Momjian <bruce@momjian.us>
Date: Wed, 22 Jun 2022 18:33:26 +0000 (-0400)
Subject: doc: clarify wording about phantom reads
X-Git-Tag: REL_10_22~45
X-Git-Url: http://git.postgresql.org/gitweb/?a=commitdiff_plain;h=4e594a42657e4a62ed34a03ea3aa2411e39efab8;p=postgresql.git
doc: clarify wording about phantom reads
Reported-by: akhilhello@gmail.com
Discussion: https://postgr.es/m/165222922369.669.10475917322916060899@wrigleys.postgresql.org
Backpatch-through: 10
---
diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml
index 3ee6553c344..c21d7a75626 100644
--- a/doc/src/sgml/high-availability.sgml
+++ b/doc/src/sgml/high-availability.sgml
@@ -2315,7 +2315,7 @@ LOG: database system is ready to accept read only connections
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 a SQL Standard compliance issue and a technical issue.
+ both a 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 de91a85e5e8..71cb4d2bc3e 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</> happen.
+ does not allow phantom reads. This is acceptable under the SQL
+ standard because the standard specifies which anomalies must
+ <emphasis>not</emphasis> occur at certain isolation levels; higher
+ guarantees are acceptable.
The behavior of the available isolation levels is detailed in the
following subsections.
</para>