diff options
| author | Robert Haas <rhaas@postgresql.org> | 2011-10-28 11:59:55 -0400 |
|---|---|---|
| committer | Robert Haas <rhaas@postgresql.org> | 2011-10-28 12:00:50 -0400 |
| commit | e489c000d90d96b415f3309c0ba423a1584503bf (patch) | |
| tree | b02348410d30d5fc38f743dedc13ceae4fd18d57 | |
| parent | ce6fb7b8e1286796f0b808446a8a84b4102a891d (diff) | |
Change "and and" to "and".
Report by Vik Reykja, patch by Kevin Grittner.
| -rw-r--r-- | doc/src/sgml/mvcc.sgml | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/src/sgml/mvcc.sgml b/doc/src/sgml/mvcc.sgml index 1ec07dd9eee..b311d240109 100644 --- a/doc/src/sgml/mvcc.sgml +++ b/doc/src/sgml/mvcc.sgml @@ -547,7 +547,7 @@ SELECT SUM(value) FROM mytab WHERE class = 2; If either transaction were running at the Repeatable Read isolation level, both would be allowed to commit; but since there is no serial order of execution consistent with the result, using Serializable transactions will allow one - transaction to commit and and will roll the other back with this message: + transaction to commit and will roll the other back with this message: <screen> ERROR: could not serialize access due to read/write dependencies among transactions |