Re: serial + db key, or guid?
| От | Adam Brusselback |
|---|---|
| Тема | Re: serial + db key, or guid? |
| Дата | |
| Msg-id | CAMjNa7cA1OMOzw6mkN8KAUabAsOaPjh2JLGrvOFS9K=SmE9cww@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: serial + db key, or guid? (Christopher Browne <cbbrowne@gmail.com>) |
| Ответы |
Re: serial + db key, or guid?
|
| Список | pgsql-general |
I mentioned this in another email thread yesterday about a similar topic, but I'd highly suggest if you do go the UUID route, do not use the standard UUID generation functions, they all suck for database use (v1 also sucks).
I use: https://pgxn.org/dist/sequential_uuids/ written by Thomas Vondara (writeup here: https://2ndquadrant.com/en/blog/sequential-uuid-generators/ )
I don't mind having a time component correlated with my UUID's because it's simply not a threat model that matters for my use case, so I use the time based variant. It helped me immensely with FPW and
write amplification when I switched from V4 UUIDs. It is still not as fast as an int, but it is much much better than random UUIDs.
В списке pgsql-general по дате отправления: