> When do you not have concurrency? Highly concurrent updates? By that I understand a workload where you have multiple clients updating the same rows. In my e

> When do you not have concurrency? Highly concurrent updates? By that I understand a workload where you have multiple clients updating the same rows. In my experience it's either rare or the result of doing something inefficiently (e.g., doing analytics as a "view_count" column). Everytime I've faced that I've remodeled the database, both for performance (you avoid invalidating caches for the entire table) and auditing reasons (if you have a bunch of people replacing each other's changes, you might want to retain the history).