We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We don't need per-block deletion limits in our pruner, because freelist isn't an issue anymore.
Before, it was introduced to not prune too many blocks, so that data from new blocks occupies >= pages in the database that was pruned.
Now, we don't care about freelist growing, so we can set the deletion limits per run, and remove all logic related to block accounting.
No response
The text was updated successfully, but these errors were encountered:
why don't we care ab freelist anymore?
Sorry, something went wrong.
the size doesn't affect performance anymore, so we can grow it as much as we want, and new data will occupy the freed pages when needed
shekhirin
Successfully merging a pull request may close this issue.
Describe the feature
We don't need per-block deletion limits in our pruner, because freelist isn't an issue anymore.
Before, it was introduced to not prune too many blocks, so that data from new blocks occupies >= pages in the database that was pruned.
Now, we don't care about freelist growing, so we can set the deletion limits per run, and remove all logic related to block accounting.
Additional context
No response
The text was updated successfully, but these errors were encountered: