tursodatabase / tursodatabase/libsql
WAL frame overwriting in sync protocol?
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 17.2k
- Forks
- 531
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 1
Description
@sivukhin writes:
SQLite can overwrite frame written inside the WAL instead of appending it to the end if this page were already written within current transaction
We currently allow syncing WAL pages from in-flight transactions, which we either need to prevent or add support for overwriting.
Contributor guide
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 by tracing how WAL pages from in-flight transactions are synchronized and compare that flow with SQLite's frame-overwriting behavior. Determine whether the intended resolution is to prevent syncing those pages or to support overwriting, then verify the chosen behavior for pages already written in the current transaction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sqlite
- Domain
- databases, distributed-systems
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100