News for hackers. Stuff that matters.

A comment on Exploring PostgreSQL 18's new UUIDv7 support. Parent comment

Re:Exploring PostgreSQL 18's new UUIDv7 support by crazygringo on Friday October 17, 2025 @06:40PM (#45622974)
> I suspect it would not be used as often as the primary key index

That doesn't matter because it's the creation of the index entry that matters, not how often it's used for lookup. The lookup cost is the same anyways.

[ Parent | on HN ]
Re:Exploring PostgreSQL 18's new UUIDv7 support by matthew16550 on Friday October 17, 2025 @07:11PM (#45623232)
The page I linked shows uses after creation where the cost can be different.
[ Parent | on HN ]
Re:Exploring PostgreSQL 18's new UUIDv7 support by crazygringo on Saturday October 18, 2025 @03:10PM (#45629672)
Making the assumption:

> Since workloads commonly are interested in recently inserted rows

That's only true for very specific types of applications. There's nothing general about that.

Plenty of applications grab rows from all time, and there's nothing special about the most recent ones. The most recent might also be the least popular rows, since few things reference them.

[ Parent | on HN ]