> Not sure about "most". Referential integrity is a pretty common use > case, and it is not covered without explicit locking. Many other > common use cases are not, either. I agree many are, and that the rest > can be worked around easily enough that I wouldn't want to see > blocking introduced to the degree that non-MVCC databases use for > serializable access.
What do you mean by referential integrity? I don't believe you can construct a foreign key problem at any transaction isolation level. ...Robert -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
