Greg Slepak@taoeffect@crib.social: @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.

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

Note Detail

Reply to @taoeffect@crib.social
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
---Reply---
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.


---Replies---

silverpill@silverpill@mitra.social (2026-04-02 05:08:03)
@taoeffect @phnt

mitra.social (4.5 years old instance):# du -sh /var/lib/postgresql/
1.2G    /var/lib/postgresql/