Report what a prune run frees - #13
Open
StanBarrows wants to merge 1 commit into
Open
Conversation
"Pruned 497 entries" says the command ran; "freeing 417 MB of payload" says what the night was worth. Measured in SQL before the UPDATE empties it — only the sum ever crosses into PHP — and reported as payload bytes rather than as a file-size before/after, which Postgres would keep flat until a VACUUM and so would read as the prune having done nothing. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
1 participant
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.
Follow-up to #12:
backlog:prunenow says what it removed, measured in SQL before the UPDATE empties it:Demonstrated against the production dump: table 2,510 MB → prune (7-day window) frees 417 MB → 2,079 MB after VACUUM FULL. Payload bytes rather than file-size before/after, because Postgres holds the file flat until a VACUUM and the report would read as a no-op.
Tests cover the exact byte count; suite stays at 100% coverage.
🤖 Generated with Claude Code