public inbox for [email protected]
help / color / mirror / Atom feedFrom: David Fetter <[email protected]>
To: PostgreSQL Docs <[email protected]>
To: PostgreSQL Patches <[email protected]>
Subject: Predicate Locking
Date: Fri, 1 Sep 2006 10:30:55 -0700
Message-ID: <[email protected]> (raw)
Folks,
This patch clarifies the 'predicate locking' section in the docs.
Thanks to Harrison Fisk of MySQL AB for helping.
Cheers,
D
--
David Fetter <[email protected]> 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>
Attachments:
[text/plain] mvcc_predicate_locking.patch (1.2K, 2-mvcc_predicate_locking.patch)
download | inline diff:
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>
view thread (3+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: Predicate Locking
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox