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