tursodatabase/turso

Ensure `VACUUM INTO` works with rich / custom types

Open

#5,898 opened on Mar 12, 2026

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Rust (1,001 forks)github user discovery
good first issuetestingvector search

Repository metrics

Stars
 (19,103 stars)
PR merge metrics
 (PR metrics pending)

Description

Those introduced here: https://github.com/tursodatabase/turso/pull/5254 and https://github.com/tursodatabase/turso/pull/5729. The types are quite rich, support a lot of things. We must ensure vacuum into supports all these.

While at it, we must also make sure that vector types work with vacuum into

if they work out of the box, lets add tests.

Contributor guide

Research direction
Study the custom types implemented in PRs #5254 and #5729, understand the VACUUM INTO code path, and write tests to verify compatibility with all custom types including vectors.
Tech stack
rust
Domain
database
Issue type
Test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
RustGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65