public inbox for [email protected]
help / color / mirror / Atom feedRepeatable Read Table Reference
2+ messages / 2 participants
[nested] [flat]
* Repeatable Read Table Reference
@ 2016-05-24 20:38 [email protected]
2016-05-25 16:23 ` Re: Repeatable Read Table Reference Kevin Grittner <[email protected]>
0 siblings, 1 reply; 2+ messages in thread
From: [email protected] @ 2016-05-24 20:38 UTC (permalink / raw)
To: pgsql-docs
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/9.5/static/transaction-iso.html
Description:
In the documentation for Repeatable Read on this page:
https://www.postgresql.org/docs/current/static/transaction-iso.html
The documentation says, "This is a stronger guarantee than is required by
the SQL standard for this isolation level, and prevents all of the phenomena
described in Table 13-1."
Since the Serialization Anomaly was added to the table in this commit
(https://github.com/postgres/postgres/commit/23c33198b961f27c80655a7cf439d49ef5a1833d#diff-a85793bf15...),
that statement is no longer true if I understand the documentation
correctly. Here's a brief patch to tweak that sentence.
diff --git a/doc/src/sgml/mvcc.sgml b/doc/src/sgml/mvcc.sgml
index f2272bc..0a112cb 100644
--- a/doc/src/sgml/mvcc.sgml
+++ b/doc/src/sgml/mvcc.sgml
@@ -461,10 +461,10 @@ COMMIT;
even though they are not yet committed.) This is a stronger
guarantee than is required by the <acronym>SQL</acronym> standard
for this isolation level, and prevents all of the phenomena described
- in <xref linkend="mvcc-isolevel-table">. As mentioned above, this is
- specifically allowed by the standard, which only describes the
- <emphasis>minimum</emphasis> protections each isolation level must
- provide.
+ in <xref linkend="mvcc-isolevel-table"> except for serialization
+ anomalies. As mentioned above, this is specifically allowed by the
+ standard, which only describes the <emphasis>minimum</emphasis>
+ protections each isolation level must provide.
</para>
<para>
--
Sent via pgsql-docs mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: Repeatable Read Table Reference
2016-05-24 20:38 Repeatable Read Table Reference [email protected]
@ 2016-05-25 16:23 ` Kevin Grittner <[email protected]>
0 siblings, 0 replies; 2+ messages in thread
From: Kevin Grittner @ 2016-05-25 16:23 UTC (permalink / raw)
To: [email protected]; +Cc: pgsql-docs
On Tue, May 24, 2016 at 3:38 PM, <[email protected]> wrote:
> In the documentation for Repeatable Read on this page:
>
> https://www.postgresql.org/docs/current/static/transaction-iso.html
>
> The documentation says, "This is a stronger guarantee than is required by
> the SQL standard for this isolation level, and prevents all of the phenomena
> described in Table 13-1."
>
> Since the Serialization Anomaly was added to the table in this commit
> (https://github.com/postgres/postgres/commit/23c33198b961f27c80655a7cf439d49ef5a1833d#diff-a85793bf15...),
> that statement is no longer true if I understand the documentation
> correctly. Here's a brief patch to tweak that sentence.
Pushed. Thanks!
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-docs mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2016-05-25 16:23 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2016-05-24 20:38 Repeatable Read Table Reference [email protected]
2016-05-25 16:23 ` Kevin Grittner <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox