>>> Tom Lane <t...@sss.pgh.pa.us> wrote: > Huh? Deadlocks were not the issue here. What you asked for was a > failure if someone else had updated the rows you're selecting for > update. Logically, these are both forms of serialization failure when doing SELECT FOR UPDATE in READ COMMITTED mode. One currently deadlocks, generating an error that requires a retry. The other quietly fails to return the requested results. I'm suggesting that it would be better to generate an error with an indication of the serialization failure. You said that people use READ COMMITTED to avoid such errors. I'm pointing out that they can currently get serialization failure errors in READ COMMITTED if they choose to SELECT FOR UPDATE. -Kevin
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
