Fixing Uuidv7 (for Database Use-Cases)
Posted3 months agoActive3 months ago
brooker.co.zaTechstory
calmpositive
Debate
20/100
Uuidv7Database DesignDistributed Systems
Key topics
Uuidv7
Database Design
Distributed Systems
The article discusses potential improvements to UUIDv7 for database use-cases, and the single comment provides a nuanced perspective on the proposed changes.
Snapshot generated from the HN discussion
Discussion Activity
Light discussionFirst comment
4h
Peak period
1
3-4h
Avg / period
1
Key moments
- 01Story posted
Oct 23, 2025 at 12:27 AM EDT
3 months ago
Step 01 - 02First comment
Oct 23, 2025 at 4:15 AM EDT
4h after posting
Step 02 - 03Peak activity
1 comments in 3-4h
Hottest window of the conversation
Step 03 - 04Latest activity
Oct 23, 2025 at 4:15 AM EDT
3 months ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
Discussion (1 comments)
Showing 1 comments
sergeyprokhoren
3 months ago
The PostgreSQL uuidv7() developers are leaning toward a different approach to solving timestamp leaks, similar to FHSS (https://en.wikipedia.org/wiki/Frequency-hopping_spread_spect...). This is currently possible manually using the parameter "shift" (https://postgrespro.ru/docs/postgresql/18/functions-uuid), but could be automated in the near future
View full discussion on Hacker News
ID: 45678169Type: storyLast synced: 11/17/2025, 9:12:00 AM
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.