Re: Predicate Locking

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-docs(at)postgresql(dot)org, David Fetter <david(at)fetter(dot)org>, PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: Predicate Locking
Date: 2006-09-03 01:58:52
Message-ID: 200609030158.k831wqD00788@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs pgsql-patches

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,
<productname>PostgreSQL</productname> does not implement predicate
locking.

--
Bruce Momjian bruce(at)momjian(dot)us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Browse pgsql-docs by date

  From Date Subject
Next Message Tom Lane 2006-09-03 19:06:15 pgsql: Fix non-improvement of description of archive_timeout.
Previous Message Peter Eisentraut 2006-09-01 22:31:57 Re: Predicate Locking

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2006-09-03 03:22:35 Re: [COMMITTERS] pgsql: Change FETCH/MOVE to use int8.
Previous Message Bruce Momjian 2006-09-03 01:56:16 Re: SSL enhancement patch ver.2