Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit d387a07

Browse files
committed
Update predicate locking text.
1 parent 1d4abf2 commit d387a07

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

doc/src/sgml/mvcc.sgml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
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 $ -->
22

33
<chapter id="mvcc">
44
<title>Concurrency Control</title>
@@ -469,9 +469,9 @@ SELECT SUM(value) FROM mytab WHERE class = 2;
469469
transaction. And this large expense is mostly wasted, since in
470470
practice most applications do not do the sorts of things that could
471471
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,
473473
<productname>PostgreSQL</productname> does not implement predicate
474-
locking, and so far as we are aware no other production DBMS does either.
474+
locking.
475475
</para>
476476

477477
<para>

0 commit comments

Comments
 (0)