>From 311ea8a493c939a70a89234246f662514687d8c2 Mon Sep 17 00:00:00 2001
From: Craig Ringer <ringerc@ringerc.id.au>
Date: Sat, 18 Aug 2012 12:51:28 +0800
Subject: [PATCH 1/3] Make sure you can't read through mvcc.sgml without
 realising that not everything is MVCC.

---
 doc/src/sgml/mvcc.sgml | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/doc/src/sgml/mvcc.sgml b/doc/src/sgml/mvcc.sgml
new file mode 100644
index 8f88582..9dc65f5
*** a/doc/src/sgml/mvcc.sgml
--- b/doc/src/sgml/mvcc.sgml
***************
*** 260,265 ****
--- 260,277 ----
      command <xref linkend="sql-set-transaction">.
     </para>
  
+    <important>
+      <para>
+        Some <productname>PostgreSQL</productname> data types and functions have
+        special rules regarding transactional behaviour.  In particular, changes
+        made to a <literal>SEQUENCE</literal> (and therefore the counter of a
+        <literal>SERIAL</literal>) are immediately visible to all other
+        transactions and are not rolled back if the transaction that made the
+        changes aborts.  See <xref linkend="functions-sequence"> and
+        <xref linkend="datatype-serial">.
+      </para>
+    </important>
+ 
    <sect2 id="xact-read-committed">
     <title>Read Committed Isolation Level</title>
  
-- 
1.7.11.2