From: Tom Lane <tgl@sss.pgh.pa.us>
To: Daniel Roth <dan.c.roth@gmail.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: predicate locking
Date: Sun, 12 Jun 2005 23:04:29 -0400
Message-ID: <10450.1118631869@sss.pgh.pa.us> (raw)
In-Reply-To: <71038fca0506121916764f5b33@mail.gmail.com>
References: <71038fca05061203395e5a2613@mail.gmail.com>
<23768.1118588642@sss.pgh.pa.us>
<71038fca0506121916764f5b33@mail.gmail.com>
Daniel Roth <dan.c.roth@gmail.com> writes:
> It sates: "To guarantee true mathematical serializability, it is
> necessary for a database system to enforce predicate locking, which
> means that a transaction cannot insert or modify a row that would have
> matched the WHERE condition of a query in another concurrent
> transaction"
> Now that is exactly whats happens when you use SERIALIZABLE is MSSQL.
Only for WHERE conditions that can be expressed as a simple range
constraint.
> All I am trying to do is correct the help documentation - 12.2.2.1 "so
> far as we are aware no other production DBMS does either."
The documentation is not wrong; or at least, what you've quoted does not
show that it is.
regards, tom lane
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: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, dan.c.roth@gmail.com
Subject: Re: predicate locking
In-Reply-To: <10450.1118631869@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox