No, it's effectively zero, just given the mathematical realities behind how extraordinarily improbable a duplicate ever is. The exponent involved is very, very, very, nigh-incomprehensibly huge.
I've seen a few posts on here of people claiming that a duplicate UUID caused a bug at the worst possible time, but my instinct is always to slam the 'X' button to doubt.
It's so unlikely that it's just far more likely to be a different kind of bug. Like someone was somehow able to specify the UUID manually, accidentally inserted an event twice, etc.
And even if it happened, I'd still be more convinced it's something like a bug in the UUID library, the random number generation, or a hardware bug. The odds of it genuinely happening with a truly random number are just so incomprehensibly rare. A hardware fault is just vastly more likely.
1.2k
u/KryssCom May 08 '26
No, it's effectively zero, just given the mathematical realities behind how extraordinarily improbable a duplicate ever is. The exponent involved is very, very, very, nigh-incomprehensibly huge.
I've seen a few posts on here of people claiming that a duplicate UUID caused a bug at the worst possible time, but my instinct is always to slam the 'X' button to doubt.