public inbox for [email protected]
help / color / mirror / Atom feedFrom: Bruce Momjian <[email protected]>
To: Srinath Reddy Sadipiralla <[email protected]>
Cc: PostgreSQL-development <[email protected]>
Subject: Re: First draft of PG 19 release notes
Date: Tue, 16 Jun 2026 19:41:23 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAFC+b6pLBJx9PyNAGOFjFJRN5sEnNm9G2O5tK0VCUZ_9mitEkw@mail.gmail.com>
References: <[email protected]>
<CAFC+b6pLBJx9PyNAGOFjFJRN5sEnNm9G2O5tK0VCUZ_9mitEkw@mail.gmail.com>
On Thu, Jun 11, 2026 at 02:31:38PM +0530, Srinath Reddy Sadipiralla wrote:
> Hi Bruce,
>
> On Wed, Apr 15, 2026 at 6:49 AM Bruce Momjian <[email protected]> wrote:
>
> I have completed the first draft of the PG 19 release notes:
>
> https://www.postgresql.org/docs/devel/release-19.html
>
>
> Thanks for working on this.
>
> I noticed the notes don't mention the pg_rewind improvement committed in
> 5173bfd0 ("pg_rewind: Skip copy of WAL segments generated before point of
> divergence") [0].
>
> [0] - https://www.postgresql.org/message-id/flat/
> 181b4c6fa9c.b8b725681941212.7547232617810891479%40viggy28.dev
True. In reading the commit message, it seems like a minor improvement
that wasn't worth mentioning; it says:
This commit makes the way WAL segments are handled from the source
to the target server slightly smarter:
----------------
and
This change can make the rewind operation cheaper in some
configurations, especially for setups where some WAL retention
causes many segments to remain on the source server even after the
promotion of a standby used as source to rewind a previous primary.
It seemed like a nice improvement, but not something that would be
useful for the average user to know.
--
Bruce Momjian <[email protected]> https://momjian.us
EDB https://enterprisedb.com
Do not let urgent matters crowd out time for investment in the future.
view thread (26+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: First draft of PG 19 release notes
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox