4 ms·
We discussed some of these problems here during a Postgres.tv session, and developed a patch to support ULID / UUIDv7: https://www.youtube.com/watch?v=YPq_hiOE-
by samokhvalov 3y ago
We discussed some of these problems here during a Postgres.tv session, and developed a patch to support ULID / UUIDv7: https://www.youtube.com/watch?v=YPq_hiOE-N8 https://www.youtube.com/watch?v=YPq_hiOE-N8
And then Andrey proposed a patch in the pgsql-hackers mailing list: https://www.postgresql.org/message-id/flat/CAAhFRxitJv%3DyoGnXUgeLB_O%2BM7J2BJAmb5jqAT9gZ3bij3uLDA%40mail.gmail.com https://www.postgresql.org/message-id/flat/CAAhFRxitJv%3DyoG..., https://commitfest.postgresql.org/43/4388/ https://commitfest.postgresql.org/43/4388/
Everyone who can help (test, discuss, etc.) – please participate in that discussion.
The standard is not finalized yet, but there some expectations that it will be, if it happens, it would be great to have this in future Postgres 17.
- pksunkara 3y agoImplementing support for UUIDv7 does not equal implementing support for ULID. ULID needs to be treated as a first class citizen (type, read format, storage format, converters) instead of being an afterthought result from UUIDv7. I have built a postgres extension for adding ULID support which does what I described. https://github.com/pksunkara/pgx_ulid https://github.com/pksunkara/pgx_ulid