Greg Slepak@taoeffect@crib.social: Here are the hoops I have to jump through: <a class="link-in-note" href="https://git.pleroma.social/pleroma/pleroma/issues/2338#issuecomment-115204" target="_blank" rel="nofollow noopener">https://git.pleroma.social/pleroma/pleroma/issues/2338#issuecomment-115204</a>

Home | Notifications | New Note | Local | Federated | Search | Logout

Note Detail

Greg Slepak@taoeffect@crib.social (2026-04-02 01:18:26)
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.
---Reply---
Greg Slepak@taoeffect@crib.social (2026-04-02 03:08:53)
Here are the hoops I have to jump through: https://git.pleroma.social/pleroma/pleroma/issues/2338#issuecomment-115204


---Replies---

Greg Slepak@taoeffect@crib.social (2026-04-02 04:55:58)
@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.