From d387a0705058af6d07390dec5cb56a4720a302a6 Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Sun, 3 Sep 2006 01:59:09 +0000
Subject: [PATCH] Update predicate locking text.
---
doc/src/sgml/mvcc.sgml | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/doc/src/sgml/mvcc.sgml b/doc/src/sgml/mvcc.sgml
index 1a1e95db501..eba07a80dad 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>
--
GitLab