Re: Add errdetail() with PID and UID about source of termination signal - Mailing list pgsql-hackers

From Jacob Champion
Subject Re: Add errdetail() with PID and UID about source of termination signal
Date
Msg-id CAOYmi+=vsp1reDVo77e9Nx0=kb7hiaPP0jOzMiHWDDM6=afzug@mail.gmail.com
Whole thread
In response to Re: Add errdetail() with PID and UID about source of termination signal  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: Add errdetail() with PID and UID about source of termination signal
List pgsql-hackers
On Wed, Apr 15, 2026 at 7:17 AM Andrew Dunstan <andrew@dunslane.net> wrote:
> OK, pushed. Thanks.

I hit the following in the pg_basebackup tests just now, running on Linux:

    [08:41:21.621](0.377s) ok 196 - Walsender killed
    [09:09:11.134](1669.513s) # pump_until: timeout expired when
searching for "(?^:background process terminated unexpectedly)" with
stream: "pg_basebackup: error: unexpected termination of replication
stream: FATAL:  terminating connection due to administrator command
    # DETAIL:  Signal sent by PID 155573, UID 1000.
    # "
    [09:09:11.134](0.000s) not ok 197 - background process exit message
    [09:09:11.134](0.000s) #   Failed test 'background process exit message'
    #   at src/postgres/src/bin/pg_basebackup/t/010_pg_basebackup.pl line 1049.

But I haven't been able to reproduce since, so I don't know if this is
a new race, or the commit just exposed one that was there before?

Thanks,
--Jacob



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Add errdetail() with PID and UID about source of termination signal
Next
From: Heikki Linnakangas
Date:
Subject: Re: [PATCH] postmaster: fix stale PM_STARTUP comment