From: Bruce Momjian <bruce@momjian.us>
Date: Sun, 3 Sep 2006 01:59:09 +0000 (+0000)
Subject: Update predicate locking text.
X-Git-Tag: REL8_2_BETA1~184
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=d387a0705058af6d07390dec5cb56a4720a302a6;p=postgresql

Update predicate locking text.
---

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