Skip to content

Consider recommending VACUUM for SQLite database maintenance #2927

@aryklein

Description

@aryklein

Hi there,

I noticed that over time, the ~/.local/share/atuin/history.db file can grow quite large. Out of curiosity, I ran the following command:

sqlite3 ~/.local/share/atuin/history.db "VACUUM;"

Afterward, the database size was significantly reduced.

Would it make sense for Atuin to:

Recommend running VACUUM in the docs as a maintenance step?
Or possibly run it automatically in some scenarios (e.g. after deleting a large amount of history)?

I’m not sure if there are trade-offs (like performance implications or locking concerns), but it seems like it could help keep storage usage efficient.

Thanks for considering this, and for the awesome project.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions