Custom freelist handling
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.6k
- Forks
- 48
- PR merge metrics
- No merged PRs in 30d
Description
SQLite manages an on-disk data structure called "[freelist](https://www.sqlite.org/fileformat.html#the_freelist)". The freelist is used to track free pages in the database.
The head of the freelist is stored in page 0. Each page allocation/release will write to page 0, and conflict with every other concurrent transaction. This is not good for concurrency.
We should emulate a freelist instead.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked SQLite file-format documentation, focusing on the freelist and page 0. Then inspect the repository's database and transaction code to determine where page allocation and release are handled. Done means freelist behavior is emulated while avoiding page 0 writes for each concurrent transaction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, sqlite
- Domain
- database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100