MarekWo f72f6d418a feat(db): VACUUM after retention and an Optimize button in Backup modal ...

SQLite DELETE marks pages free but doesn't shrink the file, so the
new retention job would keep DBs at their bloated size forever without
a follow-up VACUUM. Add db.vacuum() that runs PRAGMA-free VACUUM and
reports size_before/size_after/elapsed so callers can surface results.

The retention job now calls vacuum() automatically when it deleted at
least 1000 rows. Threshold avoids the multi-second VACUUM cost on quiet
days. Failure is logged, not raised — a missed VACUUM never crashes
the scheduler.

Power-user override: new "Optimize now" button in the Database Backup
modal triggers VACUUM on demand via POST /api/db/vacuum, alongside a
GET /api/db/size that drives the live "Current size" label. This way
users don't have to wait until 03:30 to reclaim space after the first
big retention pass.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

2026-06-07 10:55:23 +02:00

..

__init__.py

feat(retention): add message retention scheduling (Task 2.6)

2026-03-01 17:28:54 +01:00

manager.py

feat(db): VACUUM after retention and an Optimize button in Backup modal

2026-06-07 10:55:23 +02:00