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 11:04:02 -0400
Message-ID: <23768.1118588642@sss.pgh.pa.us> (raw)
In-Reply-To: <71038fca05061203395e5a2613@mail.gmail.com>
References: <71038fca05061203395e5a2613@mail.gmail.com>
Daniel Roth <dan.c.roth@gmail.com> writes:
> But MSSQL (SQL Server) does predicate locking.
> Places a range lock on the data set, preventing other users from
> updating or inserting rows into the data set until the transaction is
> complete. This is the most restrictive of the four isolation levels.
Range locks are a far cry from general predicate locks.
regards, tom lane
PS: kindly don't email me privately while posting the same message to
the lists. You think I have time to answer things twice?
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: <23768.1118588642@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