3 ms·
> Nothing wrong with 128bits primary key. Postgres is a horrible DB that can’t order rows on disk, so it doesn’t matter if you use UUIDs or not, you’re SOL. Wh
by chipdart 2y ago
> Nothing wrong with 128bits primary key. Postgres is a horrible DB that can’t order rows on disk, so it doesn’t matter if you use UUIDs or not, you’re SOL.
Why do you believe a database should order rows on disk?
- stoperaticless 2y ago1. Faster access by that column. 2. Other DBs allow it/default to it.
- hobs 2y agohttps://www.postgresql.org/docs/current/sql-cluster.html https://www.postgresql.org/docs/current/sql-cluster.html Also postgres can do this, it just doesn't maintain a clustered index as a going forward concern, which is an odd choice but postgres is certainly full of them.
- srcreigh 2y agoIn Postgres every read happens in increments of 8kb If your rows are not ordered on disk, the amount of data you need to load to query 100 rows is insane 10kb query result (100 rows 100 bytes) requires almost 1mb of data to be loaded- it’s 99% waste Postgres is 100x slower than other DBs for range queries Every single other database in existence has this feature except for Postgres