"Kevin Grittner" <kevin.gritt...@wicourts.gov> writes:
> (2) They *can* get a serialization failure involving just two
> transactions: a read and a write.
Only if you ignore the difference between SELECT FOR UPDATE/SHARE and
plain SELECT. I think calling the former a "read" is a conceptual error
to start with. It has the same locking and synchronization behavior as
a write.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
