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_aS3e7-Q+9mO5M5W8_pw-rcAgDHuNzykUSrcHw2JTh74g@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>)
List pgsql-hackers
On Mon, Apr 20, 2026 at 12:18 PM Melanie Plageman
<melanieplageman@gmail.com> wrote:
>
>
> Yes, I think changing it to a temp table is the easiest fix. We could
> also do autovacuum_enabled=false, I think, but making it a temp table
> seems cleanest.
>
> I wonder if we should move the EXPLAIN test above the results queries,
> then throw in a vacuum in between some of them so we exercise btree
> gist as a bitmap heap scan and as an index only scan. It could provide
> a little bit more coverage? Or maybe that isn't actually extra
> coverage. I'm not sure.

I kept it simple and just committed making it a temp table in 62407d26b7c

- Melanie



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: First draft of PG 19 release notes
Next
From: Melanie Plageman
Date:
Subject: Re: bufmgr: pass through I/O stats context in FlushUnlockedBuffer()