tursodatabase / tursodatabase/libsql
Expose `VACUUM` in libSQL server?
Open
Nobody has claimed this yet.
enhancement
help wanted
question
- Dominant language
- C
- Stars
- 17.2k
- Forks
- 531
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 1
Description
We currently don't allow users to control when vacuuming happens. Let's look into exposing this to users who need that level of control.
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 locating how the libSQL server currently schedules or performs vacuuming and where user-controlled database operations are exposed. Clarify the intended control surface and expected behavior for manual or configured vacuuming, then add focused coverage showing that the requested control works.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sqlite
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100