X-Original-To: pgsql-docs-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id D7DDA9FB512 for ; Fri, 1 Sep 2006 20:08:43 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 51415-01-4 for ; Fri, 1 Sep 2006 20:08:34 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by postgresql.org (Postfix) with SMTP id 46D839FB410 for ; Fri, 1 Sep 2006 19:32:00 -0300 (ADT) Received: (qmail invoked by alias); 01 Sep 2006 22:31:58 -0000 Received: from dslb-084-063-058-225.pools.arcor-ip.net (EHLO colt.pezone.net) [84.63.58.225] by mail.gmx.net (mp005) with SMTP; 02 Sep 2006 00:31:58 +0200 X-Authenticated: #495269 From: Peter Eisentraut To: pgsql-docs@postgresql.org Subject: Re: Predicate Locking Date: Sat, 2 Sep 2006 00:31:57 +0200 User-Agent: KMail/1.9.3 Cc: David Fetter , PostgreSQL Patches References: <20060901173055.GO7270@fetter.org> In-Reply-To: <20060901173055.GO7270@fetter.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200609020031.58404.peter_e@gmx.net> X-Y-GMX-Trusted: 0 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200609/2 X-Sequence-Number: 3689 David Fetter wrote: > This patch clarifies the 'predicate locking' section in the docs. What it does it raise the question what "next-key locking is". I don't think any of this matters for us. We should just remove the part that claims that no other system implements predicate locking. -- Peter Eisentraut http://developer.postgresql.org/~petere/