perf: MVCC (auto)vacuum and bulk_delete improvements #465
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.
Ticket(s) Closed
What
Finished review and rebase of @aragalie's #404. I intended to push to/merge that one, but GitHub closed it and won't let me re-open.
Why
All the notes from #404 still apply. I've spend the last day studying @aragalie's work to better understand VACUUM operations in Postgres. Carefully following the code paths with a debugger helped me verify that everything is being called as expected.
I can't find much information about @aragalie's change to increment
stats_binding.pages_deleted
instead ofstats_binding.tuples_removed
, as well as the change to incrementstats_binding.num_pages
instead ofstats_binding.num_index_tuples
. @aragalie, it would be great if you could comment on this change!Otherwise, the PR seems to work well, and I'd be in favor of merging so I can build off it for an
amdelete
implementation.