[chore] Run ANALYZE for SQLite after latest migrations

[tsmethurst]

See #2425 for more details.

We may want to run VACUUM as well, but since this can take quite a long time (10-15 minutes-ish), it might be better not to, but instead tell folks to run it manually. I'm not entirely sure yet.

[daenney]

I'm wondering if instead of doing this as a migration itself, we can see if migrations happened during startup and then trigger an analyze? That way we don't have to remember to do this after each migration.

[daenney]

But for the case of the 0.13 cycle I think this is fine. We can just merge this.

[tsmethurst]

Ack, yeah that makes sense. Let's do it properly (and perhaps include autovacuum as well) once 0.13.0 is out.

[daenney]

We can hook it here I think:

gotosocial/internal/db/bundb/bundb.go

Line 106 in 455064f

if err != nil && !strings.Contains(err.Error(), "no migrations") {