Timeline
Post
Remote status
Fetching context…
This post replies to something we haven't fetched yet. We'll try to pull in the missing thread context in the background.
@taoeffect @phnt @silverpill mitra's database is much better structured, so it doesn't grow quite as aggressively for the same amount of posts, but also have you run it through https://github.com/reorg/pg_repack or a database vacuum to actually recover the deleted space?
sadly postgresql comes from a rich lineage, where a bigger computer is the end all solution
sadly postgresql comes from a rich lineage, where a bigger computer is the end all solution
Replies
5
@i @phnt @taoeffect @silverpill As far as I know nobody also subscribed Mitra to multiple large Mastodon relays. The relay issue where Pleroma stores activities that are of no use to it (the ghost repeat), is something I have added to my list of issues (as I always forget about it). I just have to get to it one day.
@i @phnt @taoeffect @silverpill That is not the only fix needed. The Transmogrifier gets in the way I think. Besides that, having that as an optional MRF is dumb, it needs to be automatic so admins don't need to enable it and at that point it being an MRF doesn't make sense.
@phnt @phnt @taoeffect @silverpill fedi just needs a better way to federate too (tfw no nigentropy )
@i @phnt @silverpill Is pg_repack better or worse than the pg_squeeze mentioned in the issue?
https://www.cybertec-postgresql.com/en/pg_squeeze-optimizing-postgresql-storage/