Re: Emit fewer vacuum records by reaping removable tuples during pruning

Robert Haas <robertmhaas@gmail.com>

From: Robert Haas <robertmhaas@gmail.com>

To: Melanie Plageman <melanieplageman@gmail.com>

Cc: Peter Geoghegan <pg@bowt.ie>, Michael Paquier <michael@paquier.xyz>, Pg Hackers <pgsql-hackers@postgresql.org>, Andres Freund <andres@anarazel.de>

Date: 2024-01-16T19:23:07Z

Lists: pgsql-hackers

On Tue, Jan 16, 2024 at 11:28 AM Melanie Plageman
<melanieplageman@gmail.com> wrote:
> All LGTM.

Committed.

-- 
Robert Haas
EDB: http://www.enterprisedb.com

Commits

Combine FSM updates for prune and no-prune cases.
- 5eafacd2797d 17.0 landed
Remove LVPagePruneState.
- e313a6113704 17.0 landed
Move VM update code from lazy_scan_heap() to lazy_scan_prune().
- cb970240f13d 17.0 landed
Optimize vacuuming of relations with no indexes.
- c120550edb86 17.0 landed
Be more consistent about whether to update the FSM while vacuuming.
- 45d395cd75ff 17.0 landed
Remove hastup from LVPagePruneState.
- e2d5b3b9b643 17.0 landed
Use scanned_pages to decide when to failsafe check.
- 07eef53955ea 16.0 cited
Simplify lazy_scan_heap's handling of scanned pages.
- 44fa84881fff 15.0 cited
While vacuuming a large table, update upper-level FSM data every so often.
- 851a26e26637 11.0 cited