Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wZdPO-001BM8-0Q for pgsql-hackers@arkaria.postgresql.org; Tue, 16 Jun 2026 23:41:30 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wZdPM-003Ss8-2s for pgsql-hackers@arkaria.postgresql.org; Tue, 16 Jun 2026 23:41:28 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wZdPM-003Srz-1v for pgsql-hackers@lists.postgresql.org; Tue, 16 Jun 2026 23:41:28 +0000 Received: from momjian.us ([72.94.173.45]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wZdPK-00000000ohh-1AS5 for pgsql-hackers@lists.postgresql.org; Tue, 16 Jun 2026 23:41:28 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=momjian.us; s=2026010100; h=In-Reply-To:Content-Transfer-Encoding:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-ID:Content-Description; bh=9fsxF8YFlsn6S6ZVLQ4G9p8Ja3PC71/81OBhKWd7C78=; b=X2Nqc3QX/iJa+dSg9DdEpsPOiN SisXO/WfPLJAFFZUXIB0tcEGLpbMNIgrDmsWB6BbsD2D5ArxIgFh9aP3Dk2Oc1nCXipU+GnXynHiL u9nqltkEu9zR6abhtAkB8c5qbdyWx+Wk2A279H5vpk5Wvv98VoPnAxmJTa3OqiCfvL76Ts8TTE86C 7IeMSvZJxh573mMiJazaJ6lDsw8EC9c3VqQlIxieOk1ZnG/usMlRHwnO+NEnlG8WEubqOgDjOtF3E xfzoo5HW1T1U07YEdh5g4EXbyx+EOqNOaIgohkOOMT/UyhM6FOvJPIwHjUMJT5C+gm1o7qSMbjgcX oR7NnXkQ==; Received: from bruce by momjian.us with local (Exim 4.98.2) (envelope-from ) id 1wZdPH-0000000GP5o-3kE9; Tue, 16 Jun 2026 19:41:23 -0400 Date: Tue, 16 Jun 2026 19:41:23 -0400 From: Bruce Momjian To: Srinath Reddy Sadipiralla Cc: PostgreSQL-development Subject: Re: First draft of PG 19 release notes Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 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 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 https://momjian.us EDB https://enterprisedb.com Do not let urgent matters crowd out time for investment in the future.