| From: | Adam Brusselback <adambrusselback(at)gmail(dot)com> |
|---|---|
| To: | Christopher Browne <cbbrowne(at)gmail(dot)com> |
| Cc: | Christophe Pettus <xof(at)thebuild(dot)com>, Mark Phillips <mark(dot)phillips(at)mophilly(dot)com>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: serial + db key, or guid? |
| Date: | 2020-08-11 17:42:46 |
| Message-ID: | CAMjNa7cA1OMOzw6mkN8KAUabAsOaPjh2JLGrvOFS9K=SmE9cww@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Gauthier | 2020-08-11 20:57:50 | Re: How is PG replication typically used to create a High Availability (HA) config ? |
| Previous Message | Christopher Browne | 2020-08-11 17:01:54 | Re: serial + db key, or guid? |