Remember to sqlite3 gitea.db "VACUUM;"

[deade1e]

Description

As the title says. I had to move a gitea installation that previously contained sensitive information. After deleting all repos that weren't needed, a simple grep revealed that not all info were removed.

I tried all Maintenance Operations and started all Cron Tasks manually. No luck.

After issuing sqlite3 gitea.db "VACUUM;" old data was gone.

Gitea Version

1.24

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

Running gitea via docker

Database

SQLite

[TheFox0x7]

I'm not sure what's the bug here? Is there something actionable for this?

[deade1e]

I suggest that when deleting a repository, you also perform the mentioned action for "cleaning" the db.

[p7kdev]

Shouldn't the vacuum command run regularly anyway? Would it make sense to have a cron task for this as well (as for many other things)? Maybe I just couldn't find it, but it looks like Gitea itself doesn't do any vacuuming in sqlite3 yet. Since there are other cleanup tasks (e.g. cron.delete_old_system_notices) that delete data from the database, it seems to make sense to do this from time to time (even if only at startup). Perhaps also an optimize¹.

[1] https://www.sqlite.org/pragma.html#pragma_optimize

[deade1e]

It should be more a security stuff IMHO because when you delete a repo some commit messages remain in this "cache" of sqlite. VACUUM should be issued at least on each repo delete.