Skip to content

store: Fix a mistake in how pruning status is reported #6062

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 23, 2025

Conversation

lutter
Copy link
Collaborator

@lutter lutter commented Jun 17, 2025

When we start copying nonfinal entities, we need to reset the start_vid and next_vid. They don't necessarily have a direct connection to the same values for nonfinal entities; e.g., it is possible that the start_vid for nonfinal entities is smaller than the one for final entities.

This change only affects how we report the completion of prune operations; it has no effect on what gets pruned and how.

@lutter lutter requested a review from isum June 19, 2025 20:18
When we start copying nonfinal entities, we need to reset the start_vid and
next_vid. They don't necessarily have a direct connection to the same
values for nonfinal entities; e.g., it is possible that the start_vid for
nonfinal entities is smaller than the one for final entities.

This change only affects how we report the completion of prune operations;
it has no effect on what gets pruned and how.
@lutter lutter force-pushed the lutter/prune-status branch from b499f3a to 97992cb Compare June 23, 2025 22:57
@lutter lutter merged commit 97992cb into master Jun 23, 2025
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants