On Thu, Dec 17, 2009 at 5:39 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Well, it would all depend on what you're trying to do. Typical > single-row UPDATE commands aren't really affected by this problem, > and in fact the behavior is pretty much exactly what they want as > long as the WHERE conditions don't involve columns that are being > changed. > > Maybe we should replace the bit about "complex search conditions" > with something about referencing multiple rows to perform one update. > I'm not very sure what a clearer explanation would look like though.
I wonder if RETURNING hasn't created a whole new set of cases where our READ COMMITTED behaviour is bogus. I guess it's equivalent to having used SELECT FOR UPDATE. -- greg -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
