The common case is going to be many readers with a few or even a single writer. ... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		emeraldd on Jan 11, 2013 \| parent \| context \| favorite \| on: How our users exploited concurrency and how we fix... 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.

marcosdumay on Jan 11, 2013 [–]

Many DBMS have a SELECT FOR UPDATE statement just for those cases you want to lock everybody out while just reading.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact