From 627e360358e3beb67cd2f54393835f979c5e30b7 Mon Sep 17 00:00:00 2001
From: Kevin Grittner <kgrittn@postgresql.org>
Date: Wed, 25 May 2016 11:17:08 -0500
Subject: [PATCH] Update doc text to reflect new column in MVCC phenomena
 table.

Scott Wehrenberg
---
 doc/src/sgml/mvcc.sgml | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

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.