Indexing Anti-Patterns and Maintenance/SQLite VACUUM after major churn

Compact the file after heavy changes when appropriate.

Section: Maintenance tasks

SQLite VACUUM after major churn

sql
sql
VACUUM;
Explanation

Not an index command specifically, but often relevant for long-lived local databases after large deletions or churn.

Learn the surrounding workflow

Compare similar commands or jump into common fixes when this command is part of a bigger troubleshooting path.

Related commands

Same sheet · prioritizing Maintenance tasks
PostgreSQL REINDEX
Rebuild a problematic or bloated index.
OpenIn sheetsqlsame section
MySQL ANALYZE TABLE
Refresh optimizer statistics after big data shifts.
OpenIn sheetsqlsame section
Avoid duplicate or overlapping indexes
Do not keep several indexes that serve the same leading prefix needlessly.
Be careful with low-cardinality flags
A boolean by itself is often weak unless paired with something else or made partial.
Remember unused index cost
Unused indexes still hurt writes and consume disk.