Specifies the fraction of the total number of heap tuples counted in the previous statistics collection that can be inserted without incurring an index scan at the VACUUM cleanup stage. This setting currently applies to B-tree indexes only.
If no tuples were deleted from the heap, B-tree indexes are still scanned at the VACUUM cleanup stage when at least one of the following conditions is met: the index statistics are stale, or the index contains deleted pages that can be recycled during cleanup. Index statistics are considered to be stale if the number of newly inserted tuples exceeds the
vacuum_cleanup_index_scale_factor fraction of the total number of heap tuples detected by the previous statistics collection. The total number of heap tuples is stored in the index meta-page. Note that the meta-page does not include this data until VACUUM finds no dead tuples, so B-tree index scan at the cleanup stage can only be skipped if the second and subsequent VACUUM cycles detect no dead tuples.
The value can range from
vacuum_cleanup_index_scale_factor is set to
0, index scans are never skipped during VACUUM cleanup. The default value is
- PostgreSQL11 space reuse under high delete/update rate
- insert blocks with ExclusiveLock on index in Postgres
- Geoserver WFS + PostgreSQL with large table impossibly slow
- Why does &amp;amp;amp;quot;explain analyzing&amp;amp;amp;quot; this query fnish fast (showing a parallel plan), while running the actual query without &amp;amp;amp;quot;explain analyze&amp;amp;amp;quot; doesn&amp;amp;amp;#39;t?
- Error: self signed certificate when doing a migration to production