Add info logging at startup if vacuuming database #9432
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I wasn't aware Frigate did this at startup, which I think is a bit debatable from a DB maintenance perspective. Per #9424 it would be helpful to have visibility when any periodic maintenance task is running during startup. I am continuing to try and debug slow restart issues separately; startup is next on my list.
I'm aware querying the .vacuum file is also an option, but logs are far easier (and historic).