Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Concurrent sessions may lead DB using wrong 'head' on start-up #114
The DB currently uses two 'heads' (main pages). After each commit, one of these becomes alternatingly the latest 'head'.
This is wrong, because in concurrent use transactions may not commit in the order they are opened, so the latest committed TX-ID may not have the highest ID. This can lead to the DB picking the wrong head on start-up.
Impact: Definitely lost data (all of the latest TX) + the picked 'head' may represent a broken (unreadable) database.
This issue requires a database format change.