X-Original-To: pgsql-docs-postgresql.org@postgresql.org Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id 431859FB741; Fri, 1 Sep 2006 16:58:14 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 57274-02-9; Fri, 1 Sep 2006 19:57:49 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- X-Greylist: from auto-whitelisted by SQLgrey- Received: from fetter.org (start.fetter.org [66.92.188.65]) by postgresql.org (Postfix) with ESMTP id B915F9FBA66; Fri, 1 Sep 2006 14:30:56 -0300 (ADT) Received: by fetter.org (Postfix, from userid 500) id A0AD1F3CE57; Fri, 1 Sep 2006 10:30:55 -0700 (PDT) Date: Fri, 1 Sep 2006 10:30:55 -0700 From: David Fetter To: PostgreSQL Docs , PostgreSQL Patches Subject: Predicate Locking Message-ID: <20060901173055.GO7270@fetter.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="h31gzZEtNLTqOjlF" Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200609/1 X-Sequence-Number: 3688 --h31gzZEtNLTqOjlF Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Folks, This patch clarifies the 'predicate locking' section in the docs. Thanks to Harrison Fisk of MySQL AB for helping. Cheers, D -- David Fetter http://fetter.org/ phone: +1 415 235 3778 AIM: dfetter666 Skype: davidfetter Remember to vote! --h31gzZEtNLTqOjlF Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="mvcc_predicate_locking.patch" 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, PostgreSQL does not implement predicate ! locking, and so far as we are aware no other production DBMS does either. --- 471,480 ---- result in problems. (Certainly the example above is rather contrived and unlikely to represent real software.) Accordingly, PostgreSQL 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. --h31gzZEtNLTqOjlF--