Fix transaction ID wraparound

[elliotchance]

There's currently no mitigation strategy for when transaction IDs wraparound. Even though the max transaction ID is high enough that most application won't ever encounter it, it needs to be fixed for v1.0.0.

[funny-falcon]

Even though the max transaction ID is high enough that most application won't ever encounter it

PostgreSQL did think same way many years ago ))

[elliotchance]

I do remember reading about how postgres uses a freeze transaction ID. It didn't seem difficult to implement, however postgres is able to do that in the background, whereas it's probably not reasonable to do the same thing with a file.

I would be satisfied with just having the tool to repair the file (on open or manually) if feel like implementing it 😄