tursodatabase/libsql

Expose `VACUUM` in libSQL server?

Open

#1,415 opened on May 24, 2024

View on GitHub
 (0 comments) (2 reactions) (0 assignees)C (16,744 stars) (490 forks)batch import
enhancementhelp wantedquestion

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

Tech stack
csql
Domain
database
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45
Research direction
Investigate how existing SQL commands are handled in the libSQL server codebase, particularly in the query execution path. Look at the SQLite VACUUM implementation to understand its requirements. Propose a design for exposing VACUUM through the libSQL server protocol, including necessary changes to the server command handler and potential user facing options.