News for hackers. Stuff that matters.
Re:How our users exploited concurrency and how we fixed it by EvilTrout on Friday January 11, 2013 @12:06PM (#5043587)
There's a difference between a transaction that locks for writes and one that locks for reads. By default the reading is not locked in this (common) case.
Re:How our users exploited concurrency and how we fixed it by Strilanc on Friday January 11, 2013 @03:09PM (#5044681)
That's a terrible default! Ignoring read-write races is a surefire way to... well, create bugs like the one in the post.
Re:How our users exploited concurrency and how we fixed it by emeraldd on Friday January 11, 2013 @04:36PM (#5045189)
The common case is going to be many readers with a few or even a single writer. In that scenario, a read locked database would destroy any chance of operating at scale.
Re:How our users exploited concurrency and how we fixed it by marcosdumay on Friday January 11, 2013 @06:57PM (#5045758)
Many DBMS have a SELECT FOR UPDATE statement just for those cases you want to lock everybody out while just reading.