|
1 | | -<!-- $PostgreSQL: pgsql/doc/src/sgml/mvcc.sgml,v 2.74 2010/04/0307:22:55 petere Exp $ --> |
| 1 | +<!-- $PostgreSQL: pgsql/doc/src/sgml/mvcc.sgml,v 2.75 2010/05/0315:35:30 alvherre Exp $ --> |
2 | 2 |
|
3 | 3 | <chapter id="mvcc"> |
4 | 4 | <title>Concurrency Control</title> |
@@ -565,7 +565,7 @@ SELECT SUM(value) FROM mytab WHERE class = 2; |
565 | 565 | mode — but the semantics are all the same. The only real difference |
566 | 566 | between one lock mode and another is the set of lock modes with |
567 | 567 | which each conflicts (see <xref linkend="table-lock-compatibility">). |
568 | | -. Two transactions cannot hold locks of conflicting |
| 568 | + Two transactions cannot hold locks of conflicting |
569 | 569 | modes on the same table at the same time. (However, a transaction |
570 | 570 | never conflicts with itself. For example, it might acquire |
571 | 571 | <literal>ACCESS EXCLUSIVE</literal> lock and later acquire |
|