Re: "pg_ctl stop" stops working after a backend crash - Mailing list pgsql-hackers

From Tom Lane
Subject Re: "pg_ctl stop" stops working after a backend crash
Date
Msg-id 526445.1772827603@sss.pgh.pa.us
Whole thread Raw
In response to "pg_ctl stop" stops working after a backend crash  (Alexander Kuzmenkov <akuzmenkov@tigerdata.com>)
List pgsql-hackers
Alexander Kuzmenkov <akuzmenkov@tigerdata.com> writes:
> I noticed that sometimes, when I'm running the regression tests and a
> backend crashes, the postmaster can get stuck in some weird state
> where it doesn't terminate and doesn't respond to `pg_ctl stop`
> anymore. I can semi-reliably reproduce this on 18.3 using a simple
> script below.

I experimented with this a bit.  I failed to reproduce it with
your example, but it did happen once I reduced the "sleep 0.01"
to "sleep 0.001".  So apparently, the postmaster misbehaves if
the stop signal arrives soon enough after a child crash (and
the window is tight enough that it's not too surprising we
hadn't noticed).  Didn't look at the logic.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Nathan Bossart
Date:
Subject: Re: pg_dumpall --roles-only interact with other options
Next
From: Robert Haas
Date:
Subject: Re: Bypassing cursors in postgres_fdw to enable parallel plans