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

From: Melanie Plageman <melanieplageman(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Peter Geoghegan <pg(at)bowt(dot)ie>, Michael Paquier <michael(at)paquier(dot)xyz>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>
Subject: Re: Emit fewer vacuum records by reaping removable tuples during pruning
Date: 2024-01-18 14:53:12
Message-ID: CAAKRu_aM=OL85AOr-80wBsCr=vLVzhnaavqkVPRkFBtD0zsuLQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jan 17, 2024 at 5:33 PM Melanie Plageman
<melanieplageman(at)gmail(dot)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

Attachment Content-Type Size
v10-0004-Combine-FSM-updates-for-prune-and-no-prune-cases.patch text/x-patch 6.2 KB
v10-0003-Inline-LVPagePruneState-members-in-lazy_scan_pru.patch text/x-patch 13.9 KB
v10-0002-Move-VM-update-code-to-lazy_scan_prune.patch text/x-patch 10.7 KB
v10-0001-Set-would-be-dead-items-LP_UNUSED-while-pruning.patch text/x-patch 14.2 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message jian he 2024-01-18 14:59:44 Re: POC PATCH: copy from ... exceptions to: (was Re: VLDB Features)
Previous Message Robert Haas 2024-01-18 14:40:56 Re: cleanup patches for incremental backup