Re: BUG #19623: Postmaster livelocks respawning io workers when children die after crash restart; pg_ctl stop fails

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Zexin Li <lizi(dot)openmind(at)gmail(dot)com>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org, m0935388420(at)gmail(dot)com, ayushtiwari(dot)slg01(at)gmail(dot)com
Subject: Re: BUG #19623: Postmaster livelocks respawning io workers when children die after crash restart; pg_ctl stop fails
Date: 2026-08-20 02:21:47
Message-ID: aoZku8LRQ59z1PKp@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, Aug 20, 2026 at 10:44:11AM +0900, Michael Paquier wrote:
> On Thu, Aug 20, 2026 at 10:28:53AM +0900, Zexin Li wrote:
>> Thanks for the report. I think this side note, rather than the io
>> worker respawn, is the actual bug. I reproduced the silent respawn
>> loop on Linux master with a hack that makes every child die in
>> InitPostmasterChild(), and it is unchanged with io_method=sync:
>
> Would you mind sharing that, as a matter of reproducibility?

Never mind, I have reproduced it reusing a marker file in
InitPostmasterChild() to force an exit(), and then got a postmaster
spinning. :)
--
Michael

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Paquier 2026-08-20 07:06:20 Re: BUG #19623: Postmaster livelocks respawning io workers when children die after crash restart; pg_ctl stop fails
Previous Message Michael Paquier 2026-08-20 01:44:11 Re: BUG #19623: Postmaster livelocks respawning io workers when children die after crash restart; pg_ctl stop fails