An additional thing I learned when I worked on a ulid alternative over the weekend[0] is: Postgres's internal Datum type is at most 64 bits which means every uuid requires heap allocation[1] (at least until we get 128 bit machines). 0: https://bsky.app/profile/hugotunius.se/post/3m7wvfokrus2g 1: https://github.com/postgres/postgres/blob/master/src/backend...
you may be interested in this postgres extension as well https://github.com/blitss/typeid-postgres
Avoid UUID Version 4 Primary Keys in Postgres
461–463 of 463 posts
Re: Avoid UUID Version 4 Primary Keys in Postgres
#462Earlier quoted context omitted.
> To make sure I am not speaking to a bot Do grow up. > Sex is a parameter of biology, gender is a parameter of social constructs. So you assert, but until you can show the moment that gender was shown to be different from sex beyond bare assertion then I'm not willing to accept your assertion. Do you see how that works? > Gametes are not relevant. They are relevant to sex determination and hence gender, see previous…
> > To make sure I am not speaking to a bot > Do grow up. When I quote a fragment of someone else’s sentence I usually add an ellipses(…) to show that there’s more context and not imply a full statement, but you do you Since you dropped the part about me asking you to state how the thread started, I am assuming this is at least a person dropping a prompt into ChatGPT and regurgitating it without editing. Have a good…
Re: Avoid UUID Version 4 Primary Keys in Postgres
#463Wrong. Don't use B-Tree for random indexes, there's HASH index exactly for this:
CREATE INDEX [index_name] ON [table_name] USING HASH ([column_name]);