fix(db): retain tag info with cleanup#162
Merged
Merged
Conversation
This was referenced May 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Keep ipm_tag_info under the same retention policy as the other aggregated tables and add an index on created_at for efficient cleanup.
Why
ipm_tag_info is populated on every aggregation run and is queried with a created_at window in the UI, but it was not included in the retention cleanup list. That means the table would keep growing past the configured APP_RECORDS_LIFETIME even though the rest of the aggregate tables are pruned.
Change
Validation
Local data check