←back to thread

Postgres UUIDv7 and per-back end monotonicity

(brandur.org)
230 points craigkerstiens | 2 comments | 02 Jan 25 16:32 UTC | HN request time: 0.649s | source
Show context
lordofgibbons ◴[02 Jan 25 17:20 UTC] No.42576359[source]▶
What benefit does this have over something like Twitter's Snowflake, which can be used to generate distributed monotonically increasing IDs without synchronization?

We've been using an implementation of it in Go for many years in production without issues.

replies(1): >>42579121 #
1. WorldMaker ◴[02 Jan 25 21:27 UTC] No.42579121[source]▶
UUIDv7 interoperates with all the other versions of UUID. The v7 support in Postgres doesn't add a new column type, it makes the existing column type more powerful/capable. Applications that had been using UUIDv4 everywhere can get cheap Snowflake-like benefits in existing code just from switching the generator function. Most languages have a GUID or UUID class/struct that is compatibly upgradable from v4 to v7, too.
replies(1): >>42589954 #
2. akvadrako ◴[03 Jan 25 22:08 UTC] No.42589954[source]▶
Snowflake is a 64 bit integer. It doesn't need a new column type and works everywhere.