Horton

Re: out-of-order caution

Tom Lane <tgl@sss.pgh.pa.us>

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Cc: "Robert Haas" <robertmhaas@gmail.com>, "Simon Riggs" <simon@2ndquadrant.com>, "pgsql-hackers" <pgsql-hackers@postgresql.org>
Date: 2011-10-27T19:40:22Z
Lists: pgsql-hackers 
"Kevin Grittner" <Kevin.Grittner@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