Hacker News new | ask | show | jobs
by ElbertF 1692 days ago
Years ago I ran into this issue with MySQL, storing four billion rows with a unique ID.
2 comments

This is a different issue. You ran out of IDs for your row identifier. The PostgreSQL issue is that every transaction has an ID; normally this is a fairly invisible internal thing you don't need to worry about, but in some edge cases this transaction ID can causes problems. You could, in theory, run in to this issue with just one row.

I don't know how MySQL or MariaDB handles this; AFAIK it doesn't have this issue.

Was it because your primary key was an unsigned 32-bit integer and that’s not an “issue”.
True. Not the same thing but an equally disastrous outcome.