[GH-ISSUE #2986] [FR] DB maintenance and vacuum cleaning #1310

New issue

Closed

opened 2026-03-23 20:47:44 +00:00 by mirror · 2 comments

mirror commented

2026-03-23 20:47:44 +00:00

Owner

Originally created by @xfactor2000 on GitHub (Jul 12, 2023).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/2986

Description

It might already exist, but there should be some sort of vacuum cleaning for Appflowy DB. I'd hate to find myself in a situation where my DB grows out of proportion with years, especially if used actively. All deleted notes and metadata should be purged regularly to keep the database compact.

Impact

Long-term, active users

Additional Context

No response

Originally created by @xfactor2000 on GitHub (Jul 12, 2023). Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/2986 ### Description It might already exist, but there should be some sort of vacuum cleaning for Appflowy DB. I'd hate to find myself in a situation where my DB grows out of proportion with years, especially if used actively. All deleted notes and metadata should be purged regularly to keep the database compact. ### Impact Long-term, active users ### Additional Context _No response_

mirror

2026-03-23 20:47:44 +00:00

closed this issue
added the
database

new feature
labels

mirror commented

2026-03-23 20:47:44 +00:00

Author

Owner

@annieappflowy commented on GitHub (Jul 13, 2023):

Did you refer to the databases (Grid, Kanban, Calendar) in AppFlowy or a self-hosted database that manages your AppFlowy data?

@annieappflowy commented on GitHub (Jul 13, 2023): Did you refer to the databases (Grid, Kanban, Calendar) in AppFlowy or a self-hosted database that manages your AppFlowy data?

mirror commented

2026-03-23 20:47:45 +00:00

Author

Owner

@xfactor2000 commented on GitHub (Jul 14, 2023):

@annieappflowy I am not sure I can answer that question. I do know that Appflowy is built around SQLite database, which, from my observation, grows with every kanban board transaction, and, I think, with every note added. This was my biggest issue with Joplin - it wouldn't purge deleted notes, you had to run a special shell script that would do that for you.

I imagine that unless handled properly, the DB can grow to gigabytes with years, and it's a problem since I, for example, sync it to my cloud with rclone, which won't be able to upload such a huge file on each and every change. Same thing about attachments. I don't know where they're stored, but they must be purged once not referred to anymore.

@xfactor2000 commented on GitHub (Jul 14, 2023): @annieappflowy I am not sure I can answer that question. I do know that Appflowy is built around SQLite database, which, from my observation, grows with every kanban board transaction, and, I think, with every note added. This was my biggest issue with Joplin - it wouldn't purge deleted notes, you had to run a special shell script that would do that for you. I imagine that unless handled properly, the DB can grow to gigabytes with years, and it's a problem since I, for example, sync it to my cloud with rclone, which won't be able to upload such a huge file on each and every change. Same thing about attachments. I don't know where they're stored, but they must be purged once not referred to anymore.