Re: Emit fewer vacuum records by reaping removable tuples during pruning - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Emit fewer vacuum records by reaping removable tuples during pruning
Date
Msg-id ZYeT7YDwvgEkI6uS@paquier.xyz
Whole thread Raw
In response to Re: Emit fewer vacuum records by reaping removable tuples during pruning  (Melanie Plageman <melanieplageman@gmail.com>)
Responses Re: Emit fewer vacuum records by reaping removable tuples during pruning
List pgsql-hackers
On Mon, Nov 13, 2023 at 07:06:15PM -0500, Melanie Plageman wrote:
> As best I can tell, our best case scenario is Thomas' streaming read API
> goes in, we add vacuum as a user, and we can likely remove the skip
> range logic.

This does not prevent the work you've been doing in 0001 and 0002
posted upthread, right?  Some progress is always better than no
progress, and I can see the appeal behind doing 0001 actually to keep
the updates of the block numbers closer to where we determine if
relation truncation is safe of not rather than use an intermediate
state in LVPagePruneState.

0002 is much, much, much trickier..
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Morris de Oryx
Date:
Subject: Re: Are operations on real values IMMUTABLE or STABLE?
Next
From: Michael Paquier
Date:
Subject: Re: pgsql: Prevent tuples to be marked as dead in subtransactions on standb