Horton

Re: BUG #19093: Behavioral change in walreceiver termination between PostgreSQL 14.17 and 14.18

Michael Paquier <michael@paquier.xyz>

View thread
From: Michael Paquier <michael@paquier.xyz>
To: xingguo <ryanzxg@gmail.com>
Cc: Xuneng Zhou <xunengzhou@gmail.com>, Noah Misch <noah@leadboat.com>, pgsql-bugs@lists.postgresql.org, Euler Taveira <euler@eulerto.com>
Date: 2025-11-04T09:48:42Z
Lists: pgsql-bugs

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Add assertions checking for the startup process in WAL replay routines

  2. Add assertion check for WAL receiver state during stream-archive transition

  3. Add WalRcvGetState() to retrieve the state of a WAL receiver

  4. Fix unconditional WAL receiver shutdown during stream-archive transition

  5. Add test tracking WAL receiver shutdown for primary_conninfo updates

  6. Reset InstallXLogFileSegmentActive after walreceiver self-initiated exit.

  7. Replace durable_rename_excl() by durable_rename(), take two

  8. Split xlog.c into xlog.c and xlogrecovery.c.

On Tue, Nov 04, 2025 at 05:31:24PM +0800, xingguo wrote:
> I’d like to ask whether this fix will be included in the patch release for
> version 14 - specifically 14.20. I noticed the commit mentions
> Backpatch-through: 13, and I want to confirm whether that means the fix
> will be backpatched to version 13 and all subsequent supported versions.

This has been applied across all the stable branches still supported
by the community, REL_13_STABLE, so this will be included in next
week's set of minor releases.
--
Michael