Cocoa Hoto (real) my postgres database is 77GB and growing...
Timeline
Post
Remote status
@phnt probably at least half of it 
my autoprune cronjob kept failing silently and I didn't know for months
my autoprune cronjob kept failing silently and I didn't know for months
Replies
3
@Cocoa You can get a mostly accurate idea from: https://nekosat.work/phoenix/live_dashboard/ecto_stats?nav=bloat
@Cocoa Yeah, stop Pleroma when nobody is using it and vacuumdb --full --analyze --verbose pleroma the DB, then start it back up. pg_repack is another way.
Btw this will rewrite the DB files from scratch - minus bloat, so you should also have 1.5x 77GB of free space and it will take its sweet time depending on how fast your disks are. So expect it to take the time it takes to IO ~140GB of data and then few minutes for index building.