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

From: Xuneng Zhou <xunengzhou(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Noah Misch <noah(at)leadboat(dot)com>, ryanzxg(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org, Euler Taveira <euler(at)eulerto(dot)com>
Subject: Re: BUG #19093: Behavioral change in walreceiver termination between PostgreSQL 14.17 and 14.18
Date: 2025-10-31 10:50:06
Message-ID: CABPTF7UR3CTc5m0Gzkm-18qnbXTujYzCicmRatOYsMr1LQ+z3g@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi,

On Fri, Oct 31, 2025 at 11:16 AM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>
> On Fri, Oct 31, 2025 at 12:07:01AM +0800, Xuneng Zhou wrote:
> > Using a wrapper function seems better here.
>
> For a cleaner git history, the wrapper function and the assertion
> should be split as its own commit, with the actual fix applied first.
> Just an opinion.
>

It makes sense to me. I've split the patch for HEAD into three patch
sets. Please see the attached files.

> > I’ve incorporated both tests and the assertion into the patch applied to master.
> > For earlier stable branches, the test in
> > 040_standby_failover_slots_sync.pl and the assertion for
> > WAL receiver state checking are not included (if Noah agrees too). Please check.
>
> Thanks for doing that. I have extracted the test to check the "valid"
> WAL receiver shutdown case, and applied that separately.

Thanks for checking and pushing this.

Best,
Xuneng

Attachment Content-Type Size
v3-0002-Add-WalRcvGetState-function-to-retrieve-walreceiv.patch application/octet-stream 1.7 KB
v3-0001-Fix-unconditional-walreceiver-shutdown-during.patch application/octet-stream 5.8 KB
v3-0003-Add-assertion-for-walreceiver-state-invariant-in-.patch application/octet-stream 1.4 KB

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Matthias van de Meent 2025-10-31 11:22:28 Re: BUG #19098: Can't create unique gist index, where pg_indexes says that WITHOUT OVERLAPS does exacly that
Previous Message dengkai 2025-10-31 09:45:59 回复: [bug report] About create table like feature's bug