Re: eliminate xl_heap_visible to reduce WAL (and eventually set VM on-access) - Mailing list pgsql-hackers

From Melanie Plageman
Subject Re: eliminate xl_heap_visible to reduce WAL (and eventually set VM on-access)
Date
Msg-id CAAKRu_byZAQSMa3r5GD84S_q1qQPaYxwDu-kEJ3rO=qjbb-6=Q@mail.gmail.com
Whole thread
In response to Re: eliminate xl_heap_visible to reduce WAL (and eventually set VM on-access)  (Melanie Plageman <melanieplageman@gmail.com>)
Responses Re: eliminate xl_heap_visible to reduce WAL (and eventually set VM on-access)
List pgsql-hackers
On Mon, Sep 21, 2026 at 12:18 PM Melanie Plageman
<melanieplageman@gmail.com> wrote:
>
> I've tightened up the commit messages in the latest version and
> changed 0002 as you suggested. I'll commit 0001-0003 after beta4 is
> tagged tomorrow. 0004 I'm going to think about just a bit longer (and
> would be master only).

I've committed all but v2-0004. That turned out to have a bug where I
updated the prune_xid to newest_live_xid even when there were dead
items (because that code runs before we set all-visible to false due
to dead items. Attached v3 fixes that and has a patch to replace
foreach with foreach_int and foreach_node which David suggested a long
time ago and I never got around to. 0001 targets master only, 0002
targets 19 and master. I'll commit 0002 very shortly since it's so
trivial.

- Melanie

Attachment

pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: [PATCH] Use bounded GIN pending-list cleanup in parallel autovacuum
Next
From: David Rowley
Date:
Subject: Re: Set calcSumX2 = true in numeric_(poly_)deserialize