Re: BUG #19093: Behavioral change in walreceiver termination between PostgreSQL 14.17 and 14.18 - Mailing list pgsql-bugs

From Michael Paquier
Subject Re: BUG #19093: Behavioral change in walreceiver termination between PostgreSQL 14.17 and 14.18
Date
Msg-id aQmGeVLYl51y1m_0@paquier.xyz
Whole thread Raw
In response to Re: BUG #19093: Behavioral change in walreceiver termination between PostgreSQL 14.17 and 14.18  (Xuneng Zhou <xunengzhou@gmail.com>)
Responses Re: BUG #19093: Behavioral change in walreceiver termination between PostgreSQL 14.17 and 14.18
List pgsql-bugs
On Sat, Nov 01, 2025 at 08:44:55AM +0800, Xuneng Zhou wrote:
> On Sat, Nov 1, 2025 at 8:17 AM Michael Paquier <michael@paquier.xyz> wrote:
>> Thanks, that looks sensible.  I'll revisit what you have at the
>> beginning of next week (local Tuesday) with a backpatch down to v13 in
>> mind.  If others have comments and/or objections, please feel free to
>> chime in.
>
> It's an oversight. Thanks for catching it.

Phew, done.  While looking at the whole thing, I was wondering if we
should strengthen a little bit what's expected of the context for some
of the callers of the WAL routines, like XLogShutdownWalRcv(), and
finished with the bonus patch attached.  What do you think?
--
Michael

Attachment

pgsql-bugs by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: BUG #19042: Option --help not recognized at the end of command line in pg_restore
Next
From: Richard Guo
Date:
Subject: Re: BUG #19102: Assertion failure in generate_orderedappend_paths with aggregate pushdown