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

From Kirill Reshke
Subject Re: eliminate xl_heap_visible to reduce WAL (and eventually set VM on-access)
Date
Msg-id CALdSSPjuUb-kMnwjTNWXFBvBUtnu4ckOC5bOEwEWu+_mTVL3dg@mail.gmail.com
Whole thread Raw
In response to Re: eliminate xl_heap_visible to reduce WAL (and eventually set VM on-access)  (Melanie Plageman <melanieplageman@gmail.com>)
List pgsql-hackers
On Tue, 6 Jan 2026 at 22:32, Melanie Plageman <melanieplageman@gmail.com> wrote:
>
> Ah, yes, I forgot to remove that when I removed the old
> visibilitymap_set() and made visibilitymap_set_vmbits() into
> visiblitymap_set(). Done in v33.
>
> - Melanie

I think 0001-0003 and 0009-0010 are ready.

> That test creates a table, inserts tuples, accesses one page, deletes
all the data, accesses a single page again (until the table is
vacuumed, the pages will still be there and have to be scanned even
though the data is deleted). The first time we set the VM on-access,
we have to extend the VM. That VM access is an extend and not a hit.
Once we set pd_prune_xid on the page, the extend happens during the
first access (before the delete), so when we access the VM after the
delete step, that is counted as a hit and we end up with more hits in
the stats.


Good

-- 
Best regards,
Kirill Reshke



pgsql-hackers by date:

Previous
From: myzhen
Date:
Subject: Fix incorrect column name in error message for range partition bound check
Next
From: zhibin wang
Date:
Subject: Re: Fix incorrect column name in error message for range partition bound check