Re: Why clearing the VM doesn't require registering vm buffer in wal record

On Tue, Jul 14, 2026 at 3:42 PM Melanie Plageman
<melanieplageman(at)gmail(dot)com> wrote:
>
> I've also finished all branch versions of this. Each one's code
> differs, but I've managed to keep the commit messages the same, which
> should help release notes. Note that REL_19_STABLE bumps
> XLOG_PAGE_MAGIC. This would keep us from having to maintain the
> backwards compatibility code there, which I think is what we want.
> Here are those branches.

I've pushed the main commits to all branches where needed. There are
three patches remaining that I proposed for master that do assorted
validations: visibility map and PD_ALL_VISIBLE flag validations and
some validation in the WAL machinery that registered buffers get used.
I plan to commit 0001 and 0003 once my other patches have gone through
the buildfarm. I'm considering holding onto 0002 until I add
WAL-logging to the VM corruption repair code in
heap_page_fix_vm_corruption() -- without which,
wal_consistency_checking could fail for pages that had corruption
fixed.

- Melanie