3 ms·
Every write transaction ever committed to the database is assigned a unique ID, and the most recent few million transactions are kept in a "journal" table. Thi
by quinthar 10y ago
Every write transaction ever committed to the database is assigned a unique ID, and the most recent few million transactions are kept in a "journal" table. This is what allows nodes to figure out what happened while they were offline and re-execute the missing transactions. A side-effect of that is we know exactly how many write transactions have ever been committed.
- ngrilly 10y agoThat's a funny side-effect! Should I understand the transaction unique ID is an incrementing number?
- quinthar 10y agoCorrect!
- ngrilly 10y agoThanks :-)
- justinclift 10y agoOut of curiosity, what's the value that'll wrap around at?