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-a85793bf153f1f44870606f9695bc33c),
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>