alt Hacker NewsHad a recent conversation with someone about something similar…
In our case the primary index on a table was a something like a sequential ID but the table stored data from multiple tenants so each page had data from multiple tenants
Took a while to convince people that the DB was always going to read 16KB chunks so we could reduce IO by changing the primary index so it was based around an ID that was unique to the tenant
Replies
srcreigh • today at 12:29 PM
They might be used to Postgres, which doesn't have primary index.
> Took a while to convince people that the DB was always going to read 16KB chunks so we could reduce IO by changing the primary index so it was based around an ID that was unique to the tenant
Yikes. I'm mostly frontend and even to me this seems pretty clear.