diff options
| author | Peter Geoghegan <pg@bowt.ie> | 2021-02-25 14:32:18 -0800 |
|---|---|---|
| committer | Peter Geoghegan <pg@bowt.ie> | 2021-02-25 14:32:18 -0800 |
| commit | 2376361839091b0dcdcc0b77f938b809b5f21646 (patch) | |
| tree | 9e4b74bacedcfb010a754963dcc85009e93e53ad /src/backend/executor/nodeModifyTable.c | |
| parent | 301ed8812e3f8b102b85e1f5a59e95990ed9a868 (diff) | |
| download | postgresql-2376361839091b0dcdcc0b77f938b809b5f21646.tar.gz postgresql-2376361839091b0dcdcc0b77f938b809b5f21646.zip | |
VACUUM VERBOSE: Count "newly deleted" index pages.
Teach VACUUM VERBOSE to report on pages deleted by the _current_ VACUUM
operation -- these are newly deleted pages. VACUUM VERBOSE continues to
report on the total number of deleted pages in the entire index (no
change there). The former is a subset of the latter.
The distinction between each category of deleted index page only arises
with index AMs where page deletion is supported and is decoupled from
page recycling for performance reasons.
This is follow-up work to commit e5d8a999, which made nbtree store
64-bit XIDs (not 32-bit XIDs) in pages at the point at which they're
deleted. Note that the btm_last_cleanup_num_delpages metapage field
added by that commit usually gets set to pages_newly_deleted. The
exceptions (the scenarios in which they're not equal) all seem to be
tricky cases for the implementation (of page deletion and recycling) in
general.
Author: Peter Geoghegan <pg@bowt.ie>
Discussion: https://postgr.es/m/CAH2-WznpdHvujGUwYZ8sihX%3Dd5u-tRYhi-F4wnV2uN2zHpMUXw%40mail.gmail.com
Diffstat (limited to 'src/backend/executor/nodeModifyTable.c')
0 files changed, 0 insertions, 0 deletions