summaryrefslogtreecommitdiff
path: root/doc/src/sgml/mvcc.sgml
diff options
context:
space:
mode:
authorKevin Grittner <kgrittn@postgresql.org>2016-05-25 11:17:08 -0500
committerKevin Grittner <kgrittn@postgresql.org>2016-05-25 11:17:08 -0500
commit627e360358e3beb67cd2f54393835f979c5e30b7 (patch)
treebcd10cef1dd6fccdb604cfe90e95b6ed80fa54e0 /doc/src/sgml/mvcc.sgml
parent018eb027f181234be7a580e9502c40ac5ad04f77 (diff)
downloadpostgresql-627e360358e3beb67cd2f54393835f979c5e30b7.tar.gz
Update doc text to reflect new column in MVCC phenomena table.
Scott Wehrenberg
Diffstat (limited to 'doc/src/sgml/mvcc.sgml')
-rw-r--r--doc/src/sgml/mvcc.sgml3
1 files changed, 2 insertions, 1 deletions
diff --git a/doc/src/sgml/mvcc.sgml b/doc/src/sgml/mvcc.sgml
index f2272bc865..306def4a15 100644
--- a/doc/src/sgml/mvcc.sgml
+++ b/doc/src/sgml/mvcc.sgml
@@ -461,7 +461,8 @@ 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
+ 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.