From 66c8040d509c86fd2f215c06eb16d82e570d3fb6 Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Tue, 24 Mar 2015 20:56:09 -0400
Subject: [PATCH] docs: clarify when MVCC snapshot is taken
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Report by Ãlvaro Hernández Tortosa
---
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 a0d6867de0f..e43a3be6d4e 100644
--- a/doc/src/sgml/mvcc.sgml
+++ b/doc/src/sgml/mvcc.sgml
@@ -422,8 +422,9 @@ COMMIT;
<para>
This level is different from Read Committed in that a query in a
repeatable read transaction sees a snapshot as of the start of the
+ first non-transaction-control statement in the
<emphasis>transaction</>, not as of the start
- of the current query within the transaction. Thus, successive
+ of the current statement within the transaction. Thus, successive
<command>SELECT</command> commands within a <emphasis>single</>
transaction see the same data, i.e., they do not see changes made by
other transactions that committed after their own transaction started.
--
GitLab