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

Melanie Plageman <melanieplageman@gmail.com>

From: Melanie Plageman <melanieplageman@gmail.com>

To: Robert Haas <robertmhaas@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-18T14:53:12Z

Lists: pgsql-hackers

Attachments

v10-0004-Combine-FSM-updates-for-prune-and-no-prune-cases.patch (text/x-patch) patch v10-0004
v10-0003-Inline-LVPagePruneState-members-in-lazy_scan_pru.patch (text/x-patch) patch v10-0003
v10-0002-Move-VM-update-code-to-lazy_scan_prune.patch (text/x-patch) patch v10-0002
v10-0001-Set-would-be-dead-items-LP_UNUSED-while-pruning.patch (text/x-patch) patch v10-0001

On Wed, Jan 17, 2024 at 5:33 PM Melanie Plageman
<melanieplageman@gmail.com> wrote:
>
> This does mean that something is not quite right with 0001 as well as
> 0004. We'd end up checking if we are at 8GB much more often. I should
> probably find a way to replicate the cadence on master.

I believe I've done this in attached v10.

- Melanie

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