Skip site navigation (1) Skip section navigation (2)

predicate locking knowledge

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: <pgsql-patches(at)postgresql(dot)org>
Subject: predicate locking knowledge
Date: 2006-03-23 19:13:10
Message-ID: 44229EE6.EE98.0025.0@wicourts.gov (view raw or flat)
Thread:
Lists: pgsql-patches
Attached is a patch for the documentation.  We currently state that we
don't know of any production DBMS which uses predicate locking.  Current
versions of at least two commercial products (Sybase ASE and Microsoft
SQL Server) do use it.  I believe this has been true since 1990 or
earlier.

If people need documentation for this, I can pull something together. 
If you want quick confirmation, and you have access to either of the
above products, just try the test case from the documentation page this
patch modifies.  Briefly, in these products no page is ever read or
written without first acquiring a lock; in SERIALIZABLE mode all locks
are held until COMMIT or ROLLBACK.

Stating that we're not aware of it doesn't enhance our credibility with
people using these products, who can easily confirm that the "contrived"
example in our documentation does indeed generate a serialization error
in their current product.  There is also a chance, however slim, that we
could lead someone into trouble with this statement.

-Kevin



Responses

pgsql-patches by date

Next:From: Kevin GrittnerDate: 2006-03-23 19:16:33
Subject: Re: predicate locking knowledge
Previous:From: Kevin GrittnerDate: 2006-03-23 18:55:07
Subject: Re: Where does the time go?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group