>>> Jeff Davis <pg...@j-davis.com> wrote: > In fact, it's probably most similar to UPDATE ... RETURNING, which will > give the same result (that breaks atomicity or isolation, depending on > your point of view), which is correct for READ COMMITTED isolation > level. READ COMMITTED is not supposed to be able to view the work of a concurrent transactions as PARTLY applied and PARTLY committed, which is what's happening here. If one statement in a READ COMMITTED transaction sees the uncommitted view of the data and the next statement sees the committed view, that's compliant. It may not surprise someone who is intimately familiar with PostgreSQL internals for a single SELECT statement to see PART of a transactions work, but it would surprise most users, and is certainly not compliant with the standard. -Kevin
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
