| From: | Andrey Borodin <amborodin86(at)gmail(dot)com> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Cc: | brad(at)peabody(dot)io, wolakk(at)gmail(dot)com, kydavis(at)cisco(dot)com, Nikolay Samokhvalov <samokhvalov(at)gmail(dot)com> |
| Subject: | UUID v7 |
| Date: | 2023-02-10 23:57:50 |
| Message-ID: | CAAhFRxitJv=yoGnXUgeLB_O+M7J2BJAmb5jqAT9gZ3bij3uLDA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello pgsql-hackers!
As you may know there's a new version of UUID being standardized [0].
These new algorithms of UUID generation are very promising for
database performance. It keeps data locality for time-ordered values.
From my POV v7 is especially needed for users. Current standard status
is "draft". And I'm not sure it will be accepted before our feature
freeze for PG16. Maybe we could provide a draft implementation in 16
and adjust it to the accepted version if the standard is changed? PFA
patch with implementation.
What do you think?
cc Brad Peabody and Kyzer R. Davis, authors of the standard
cc Kirk Wolak and Nik Samokhvalov who requested the feature
Thanks!
Best regards, Andrey Borodin.
[0] https://datatracker.ietf.org/doc/html/draft-peabody-dispatch-new-uuid-format-04
| Attachment | Content-Type | Size |
|---|---|---|
| v1-0001-Implement-UUID-v7-as-per-IETF-draft.patch | application/octet-stream | 5.4 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2023-02-11 00:17:00 | Re: Move defaults toward ICU in 16? |
| Previous Message | Bharath Rupireddy | 2023-02-10 23:25:30 | Re: when the startup process doesn't (logging startup delays) |