Skip to content
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

store: Go back to the less clever but correct way of pruning #4153

Merged
merged 1 commit into from
Nov 9, 2022

Conversation

lutter
Copy link
Collaborator

@lutter lutter commented Nov 9, 2022

The change in aea5b57 has a logic error in that we look at a fixed number of rows from the table, filter out the ones we don't need to copy, and then insert the remaining rows. The error is that the logic assumes that if we do not insert any rows that we are done with copying, but that's wrong, since not inserting rows now just means that no rows in the batch needed to be copied even though a subsequent batch might still have such rows.

This reverts commit aea5b57.

The change in aea5b57 has a logic error in that we look at a fixed number
of rows from the table, filter out the ones we don't need to copy, and then
insert the remaining rows. The error is that the logic assumes that if we
do not insert any rows that we are done with copying, but that's wrong,
since not inserting rows now just means that no rows in the batch needed to
be copied even though a subsequent batch might still have such rows.

This reverts commit aea5b57.
@lutter lutter merged commit a3cc5b9 into master Nov 9, 2022
@lutter lutter deleted the lutter/prune branch November 9, 2022 14:39
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