From: Bruce Momjian <bruce@momjian.us>
Date: Wed, 13 Nov 2013 15:14:05 +0000 (-0500)
Subject: docs:  clarify MVCC introduction to allow for per-statement snapshots
X-Git-Tag: REL9_4_BETA1~951
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=cd8115e0090cb04380292f880adcec9c2fc2e0f3;p=postgresql

docs:  clarify MVCC introduction to allow for per-statement snapshots
---

diff --git a/doc/src/sgml/mvcc.sgml b/doc/src/sgml/mvcc.sgml
index cefd3235a6..f56eb557b1 100644
--- a/doc/src/sgml/mvcc.sgml
+++ b/doc/src/sgml/mvcc.sgml
@@ -41,12 +41,12 @@
     for developers to manage concurrent access to data.  Internally,
     data consistency is maintained by using a multiversion
     model (Multiversion Concurrency Control, <acronym>MVCC</acronym>).
-    This means that while querying a database each transaction sees
+    This means that each SQL statement sees
     a snapshot of data (a <firstterm>database version</firstterm>)
     as it was some
     time ago, regardless of the current state of the underlying data.
-    This protects the transaction from viewing inconsistent data that
-    could be caused by (other) concurrent transaction updates on the same
+    This prevents statements from viewing inconsistent data produced
+    by concurrent transactions performing updates on the same
     data rows, providing <firstterm>transaction isolation</firstterm>
     for each database session.  <acronym>MVCC</acronym>, by eschewing
     the locking methodologies of traditional database systems,