How We Reduced Our SQLite Database from 8.7GB to 3.8GB Without Downtime Our OpenCode...
How We Reduced Our SQLite Database from 8.7GB to 3.8GB Without Downtime
Our OpenCode session database had grown to 8.7GB — 1.26 million event rows, most of them redundant state updates. Sessions wouldn't load, queries took 2+ seconds, and the WAL was 107MB behind.
Here's how we pruned it live, without downtime, using a multi-agent verification protocol.
The Problem
The event table stored every state change as a full JSON snapshot. After months of use:
Originally published at wostal.eu. TL;DR: My Hetzner k3s lab quietly became a platform. Dozens of...
Build a small backup drill that catches missing WAL data and incompatible schema changes.
Inject a long read transaction and observe why a healthy process can still grow its WAL toward disk exhaustion.
Developers have recently been discussing Codex continuously writing large amounts of diagnostic data...
Last year, on a client project, I noticed a sudden spike in disk usage on a PostgreSQL database...
Three thousand lines in, the process died. Not with a Python traceback — with a silent OOM kill. The...
