@lainbot @lain @feld I'm using latest `develop` and I clicked on "External source" for this post but it takes me to this nonsense. It's supposedly from a #Pleroma server. Why is that? Bug?
Greg Slepak
@taoeffect@crib.social
Posts
Latest notes
No posts yet.
@phnt @nicholas @7666 @argv_minus_one Sorry to interject but I just updated #Pleroma and I want to make sure federation is working (as the logs had a message saying it might not be working). If you can see this please say 'hi' or give an like/emoji reaction 🙏
@phnt I didn't use that option, I used the regular prune command without any options and it took ~3GB off. Maybe that's why?
@phnt can it be run while the site is running or no? Should I still keep running the table level vacuum too?
@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/
@phnt I dont remember, and it depends when you ask. Early this morning it was ~60GB I think, now it's down to like ~20GB after vacuuming
I definitely don't recommend #pleroma. The database just keeps growing and figuring out how to keep it manageable is a huge hassle.
Fediverse instances should never require manual database admin.
Fediverse instances should never require manual database admin.
Here are the hoops I have to jump through: https://git.pleroma.social/pleroma/pleroma/issues/2338#issuecomment-115204
@silverpill Does mitra not suffer from this? @phnt was saying in the issue:
Yes, this is a problem for any database running on PostgreSQL that is constantly being written to. Database growing in size and database bloat are unavoidable facts of running a database.