{"p":"","h":{"iv":"ROXSYW+cfvEbFHu5","at":"ocxplSQjdRC3tXEtB/9/wg=="}}

Mastodon's database size can often be reduced either through Postgres' VACUUM command or the pg_repack extension, the latter usually being more effective as a lot of the size is in index bloat which VACUUM does not touch. Mind that I do not recommend running VACUUM FULL unless you absolutely need to reclaim disk space on the system.

5
Share
Share on Mastodon
Share on Twitter
Share on Facebook
Share on Linkedin
Eugen Rochko

Speaking of vacuuming, the upcoming version of Mastodon will provide admins with the option to define a content retention policy that will evict all remote posts past a defined date. A harsh, but most effective way to keep the database (and by extension, media cache) to a constant size, as far as activity by local users allows.

8
2y
Shlee-able :he_him:

@Gargron Modern Postgres supports autovacuum. Admins shouldn't need to do that.

0
2y
Mopsi

@ambassador
We could discuss a period after which photos are automatically deleted 🤔

0
2y
Baloo Uriza

@Gargron What's the difference between VACUUM and VACUUM FULL?

0
2y
Teknikal_Domain

@Gargron About index bloat, that could also be solved with a REINDEX / REINDEX CONCURRENTLY as well, correct?

0
2y
Replies