@i The answer isn't a "have you tried being less of a poor?" since I've literally told you to run the prune task if you need to. It solves the problem. If you want to archive the Fediverse, than that's your decision and disk space is part of that consideration. More archived data always equals more data. Choose one or the other.

And the prune taking too long, that's mostly an issue of shitty IO on VPSes. The prune one cawfee club took like 3 weeks and did not finish on the BuyVM crap 200 IOPS limited slab. And it finished in something like 2 days on grips'es laptop. Same with cum salon, pernia ran it on the VPS which was hosted I think on Oracle. And I assume that IO is also shit there. My IO is also shit on here, a repack takes like 5 hours on this ~30GB DB, because it is limited to 35MB/s.

The prune on the 4GB DB of pl.borked.technology on OVH's "secondary" disk limited to ~5MB/s took 8 hours to finish without a repack.

>not to mention needing even more space to fit a repack in the first place
pg_dump into a compressed file, dropdb pleroma, pg_restore.