Horton
Menu

Re: Add errdetail() with PID and UID about source of termination signal

Jacob Champion <jacob.champion@enterprisedb.com>

View thread
From: Jacob Champion <jacob.champion@enterprisedb.com>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: Jakub Wartak <jakub.wartak@enterprisedb.com>, Chao Li <li.evan.chao@gmail.com>, Andres Freund <andres@anarazel.de>, Jim Jones <jim.jones@uni-muenster.de>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2026-04-15T16:23:14Z
Lists: 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

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Only show signal-sender PID/UID detail in server log

  2. Make psql DETAIL line test unconditionally optional.

  3. Rework signal handler infrastructure to pass sender info as argument.

  4. Add errdetail() with PID and UID about source of termination signal.