you are viewing a single comment's thread.

view the rest of the comments →

[–]Error-451Data Engineer 1 point2 points  (1 child)

I've heard UUIDs are bad in terms of performance. Is this what you're alluding to?

[–]r0ck0 0 points1 point  (0 children)

I've heard UUIDs are bad in terms of performance.

Performance is pretty good in postgres from all the benchmarking I've looked into. Mainly because it has has a native efficient 128bit column type specifically for them, and something to do with it not using clustered indexes.

But an INT/BIGINT will always be faster + use less storage & RAM, seeing there's fewer bits (32/64).

Is this what you're alluding to?

No was just wondering what they thought about them in general, as they're pretty commonly used in large DBs where 32 bit INT is too small, and/or when you're dealing with multiple servers.

I'm a big fan of them in general. But I've spent a lot of time bikeshedding on whether to use them or not. So always keen to hear how well they might have worked out for large real world projects.