|
1 | | -<!-- $PostgreSQL: pgsql/doc/src/sgml/mvcc.sgml,v 2.57 2006/08/25 04:06:45 tgl Exp $ --> |
| 1 | +<!-- $PostgreSQL: pgsql/doc/src/sgml/mvcc.sgml,v 2.58 2006/09/03 01:59:09 momjian Exp $ --> |
2 | 2 |
|
3 | 3 | <chapter id="mvcc"> |
4 | 4 | <title>Concurrency Control</title> |
@@ -469,9 +469,9 @@ SELECT SUM(value) FROM mytab WHERE class = 2; |
469 | 469 | transaction. And this large expense is mostly wasted, since in |
470 | 470 | practice most applications do not do the sorts of things that could |
471 | 471 | result in problems. (Certainly the example above is rather contrived |
472 | | - and unlikely to represent real software.)Accordingly, |
| 472 | + and unlikely to represent real software.)For these reasons, |
473 | 473 | <productname>PostgreSQL</productname> does not implement predicate |
474 | | - locking, and so far as we are aware no other production DBMS does either. |
| 474 | + locking. |
475 | 475 | </para> |
476 | 476 |
|
477 | 477 | <para> |
|