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 6F42F9FB4C2; Sat, 2 Sep 2006 22:59:01 -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 65504-07; Sat, 2 Sep 2006 22:58:52 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- X-Greylist: from auto-whitelisted by SQLgrey- Received: from momjian.us (momjian.us [70.90.9.53]) by postgresql.org (Postfix) with ESMTP id 80DA29FB4C0; Sat, 2 Sep 2006 22:58:52 -0300 (ADT) Received: (from bruce@localhost) by momjian.us (8.11.6/8.11.6) id k831wqD00788; Sat, 2 Sep 2006 21:58:52 -0400 (EDT) From: Bruce Momjian Message-Id: <200609030158.k831wqD00788@momjian.us> Subject: Re: Predicate Locking In-Reply-To: <200609020031.58404.peter_e@gmx.net> To: Peter Eisentraut Date: Sat, 2 Sep 2006 21:58:52 -0400 (EDT) CC: pgsql-docs@postgresql.org, David Fetter , PostgreSQL Patches X-Mailer: ELM [version 2.4ME+ PL123] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="US-ASCII" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.104 tagged_above=0 required=5 tests=AWL, SPF_HELO_PASS, SPF_PASS X-Spam-Level: X-Archive-Number: 200609/3 X-Sequence-Number: 3690 Peter Eisentraut wrote: > 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. OK, new text is: For these reasons, PostgreSQL does not implement predicate locking. -- Bruce Momjian bruce@momjian.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. +