> I wasn't thinking about adding a new VM setting functionality to index
> only scan in particular. heapam_index_fetch_tuple() already calls
> heap_page_prune_opt() which will do pruning under certain conditions.
> I was thinking that we start updating the VM after pruning in the
> on-access case too (not just when pruning is invoked by vacuum).
I think this will need to be careful when the workload is constantly updating
and reading the same pages, as we may end up with a continuous cycle of
updates clearing the visibility-map and selects setting the visibility-map.
this may degrade the select workloads, maybe?
--
Sami Imseih
Amazon Web Services (AWS)
