public inbox for [email protected]
help / color / mirror / Atom feedFrom: Bruce Momjian <[email protected]>
To: David G. Johnston <[email protected]>
Cc: Laurenz Albe <[email protected]>
Cc: [email protected]
Cc: Pg Docs <[email protected]>
Subject: Re: correction
Date: Tue, 7 Jun 2022 19:51:20 -0400
Message-ID: <Yp/[email protected]> (raw)
In-Reply-To: <CAKFQuwZdugdJhZHkX=NJRS=DbJW8i+Px4HcvCiYVusoohiGJig@mail.gmail.com>
References: <[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<CAKFQuwZdugdJhZHkX=NJRS=DbJW8i+Px4HcvCiYVusoohiGJig@mail.gmail.com>
On Tue, Jun 7, 2022 at 02:40:41PM -0700, David G. Johnston wrote:
> On Tue, Jun 7, 2022 at 2:07 PM Bruce Momjian <[email protected]> wrote:
>
>
>
> How is this, attached?
>
>
>
> Works for me.
>
> Capital "S" in Standard as a proper name? (mind grepping this to see how
> consistent we are one way or the other, I'm not setup for that at the moment)
Well, that's a good question. Seems we use "SQL standard", and I found
one place where we capitalize "Standard", so fixed too in this patch.
--
Bruce Momjian <[email protected]> https://momjian.us
EDB https://enterprisedb.com
Indecision is a decision. Inaction is an action. Mark Batterson
Attachments:
[text/x-diff] strict.diff (1.5K, 2-strict.diff)
download | inline diff:
diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml
index c7e402765f..3df4cda716 100644
--- a/doc/src/sgml/high-availability.sgml
+++ b/doc/src/sgml/high-availability.sgml
@@ -2194,7 +2194,7 @@ HINT: You can then restart the server after making the necessary configuration
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 an SQL Standard compliance issue and a technical issue.
+ both an 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 341fea524a..112d6ce7a8 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</emphasis> happen.
+ does not allow phantom reads. This is acceptable under the SQL
+ standard because the standard specifies which anomalies must
+ <emphasis>not</enphasis> occur at certain isolation levels; higher
+ guarantees are acceptable.
The behavior of the available isolation levels is detailed in the
following subsections.
</para>
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: correction
In-Reply-To: <Yp/[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox