2 ms·
I could maybe see how it helps with indexing performance, but in terms of lookups there’s typically not going to be correlation in terms of lookups based on rec
by vlovich123 3y ago
I could maybe see how it helps with indexing performance, but in terms of lookups there’s typically not going to be correlation in terms of lookups based on record creation. Are you referring to indexing performance as locality or something else?
- tremon 3y agothere’s typically not going to be correlation in terms of lookups based on record creation Why would you think that? You think it's equally likely to need to look up a salesorder from ten years ago vs one from two weeks ago? Are Github issues from ten years ago read equally often as the ones created yesterday? Most systems have a long tail of historic data that's mainly kept as a reference.
- vlovich123 3y agoI wasn’t thinking sales orders but account ID for example. The dangers of making absolute statements around data schema design.
- sgarland 3y agoSELECT * FROM forum_post WHERE created_at > $DATE AND created_at < $DATE If you were using UUIDv7, you could even use that to get the created_at [0], although you'd likely lose the indexing unless you made a functional index on it, like this: CREATE INDEX foo_ctime_idx ON foo(extract_timestamp_from_uuid_v7(uuid_v7_col)) [0]: https://stackoverflow.com/a/75869619 https://stackoverflow.com/a/75869619
- ndriscoll 3y agoIt would make more sense to make `timestamp_to_uuid_v7` with high bits 0 and use your PK index.