diff options
| author | Bruce Momjian <bruce@momjian.us> | 2015-03-24 20:56:09 -0400 |
|---|---|---|
| committer | Bruce Momjian <bruce@momjian.us> | 2015-03-24 20:56:09 -0400 |
| commit | 66c8040d509c86fd2f215c06eb16d82e570d3fb6 (patch) | |
| tree | 8aed80975ccc21173b988ea90097eadaf3d76cdf | |
| parent | 843cd0bfe6246d94d9b34a7f36bbb76fdba87b74 (diff) | |
| download | postgresql-66c8040d509c86fd2f215c06eb16d82e570d3fb6.tar.gz postgresql-66c8040d509c86fd2f215c06eb16d82e570d3fb6.zip | |
docs: clarify when MVCC snapshot is taken
Report by Álvaro Hernández Tortosa
| -rw-r--r-- | doc/src/sgml/mvcc.sgml | 3 |
1 files changed, 2 insertions, 1 deletions
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. |