4 ms·
It’s worse with clustered indexes — all of the data experiences this issue, not just the index.
by sroussey 6y ago
It’s worse with clustered indexes — all of the data experiences this issue, not just the index.
- munk-a 6y agoAt least in Postgres you have the advantage/disadvantage that real-time clustered tables aren't a feature on offer - so that re-clustering cost is eaten on a periodic basis whenever you invoke a re-cluster operation on the table in question. Additionally re-reading things closely I believe this package wouldn't benefit databases at all since the "sortable" form appears to be the common string representation while postgres will internally store UUIDs (at least in a UUID column) as their binary values - leading to indexing still being out of order unless you specify a ::TEXT casting.