Predicate Locking

[David Fetter <david(at)fetter(dot)org>]

Folks,

This patch clarifies the 'predicate locking' section in the docs.
Thanks to Harrison Fisk of MySQL AB for helping.

Cheers,
D
-- 
David Fetter <david(at)fetter(dot)org> http://fetter.org/
phone: +1 415 235 3778        AIM: dfetter666
                              Skype: davidfetter

Remember to vote!

Index: doc/src/sgml/mvcc.sgml
===================================================================
RCS file: /projects/cvsroot/pgsql/doc/src/sgml/mvcc.sgml,v
retrieving revision 2.57
diff -c -r2.57 mvcc.sgml
*** doc/src/sgml/mvcc.sgml	25 Aug 2006 04:06:45 -0000	2.57
--- doc/src/sgml/mvcc.sgml	1 Sep 2006 17:28:28 -0000
***************
*** 471,477 ****
      result in problems.  (Certainly the example above is rather contrived
      and unlikely to represent real software.)  Accordingly,
      <productname>PostgreSQL</productname> does not implement predicate
!     locking, and so far as we are aware no other production DBMS does either.
     </para>
  
     <para>
--- 471,480 ----
      result in problems.  (Certainly the example above is rather contrived
      and unlikely to represent real software.)  Accordingly,
      <productname>PostgreSQL</productname> does not implement predicate
!     locking.  No system based on next-key locking implements it
!     either because next-key locking only helps when all your
!     predicates are point or range searches against an available
!     B-tree index.  DB2, however, does implement predicate locking.
     </para>
  
     <para>