Comment by jashmatthews
2 years ago
Clustered tables and sequential keys have their own downsides though like lock contention on the "last" page.
2 years ago
Clustered tables and sequential keys have their own downsides though like lock contention on the "last" page.
Not really a problem in practice.
Most clustered tables don’t have a single last page. For ex it’s common to order a table by (used_id,pk) so a users data is grouped together. Dropbox did this
For the ones which do have a single last page, it’s easy to remove that, you don’t have to use sequential IDs. Use a uuid.
Basically this problem only happens when you cluster globally by mistake. just don’t make that mistake.