Re: First draft of PG 19 release notes - Mailing list pgsql-hackers

From Melanie Plageman
Subject Re: First draft of PG 19 release notes
Date
Msg-id CAAKRu_bzN6ioG+h7agjCF847whVpS2WEiJB3UXAtkJ3WVXOZwA@mail.gmail.com
Whole thread
In response to First draft of PG 19 release notes  (Bruce Momjian <bruce@momjian.us>)
Responses Re: First draft of PG 19 release notes
List pgsql-hackers
On Tue, Apr 14, 2026 at 9:19 PM Bruce Momjian <bruce@momjian.us> wrote:
>
> I have completed the first draft of the PG 19 release notes:
>
>         https://www.postgresql.org/docs/devel/release-19.html

As of b46e1e54d078def, SELECT queries may update the visibility map.
Previously only vacuum did this. I think users may be confused by this
if it is not mentioned in the release notes.

Additionally, users may notice that there are no longer
XLOG_HEAP2_VISIBLE records. A series of commits culminating in
a881cc9c7e819fb (others being d96f87332b378, add323da40a6bf9e0,
1252a4ee2863673, a759ced2f1e) moved VM setting into the
XLOG_HEAP2_PRUNE_VACUUM_SCAN record. Users may notice that
XLOG_HEAP2_VISIBLE records are no longer produced.

This is more minor, but we also now (378a216187aea1) set pd_prune_xid
on insert, so users may notice that a freshly inserted page is
on-access pruned and then the VM is set (which wouldn't have happened
before without vacuum).

- Melanie



pgsql-hackers by date:

Previous
From: Paul A Jungwirth
Date:
Subject: Re: SQL:2011 Application Time Update & Delete
Next
From: Ayush Tiwari
Date:
Subject: Re: [PATCH] postmaster: fix stale PM_STARTUP comment