Horton
Menu

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

Jim Jones <jim.jones@uni-muenster.de>

View thread
From: Jim Jones <jim.jones@uni-muenster.de>
To: Jakub Wartak <jakub.wartak@enterprisedb.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2026-02-18T16:08:25Z
Lists: pgsql-hackers 
Hi Jakub

On 18/02/2026 08:32, Jakub Wartak wrote:
> I would first like to learn if that would be a welcomed feature or not.

+1

I think it's a very useful feature (only tested on Linux)

FATAL:  terminating connection due to administrator command
DETAIL:  signal sent by PID 1592705, UID 1000.

I'm wondering if there is a standard style for displaying such values in
DETAIL. For instance, the checkpoint LOG is formatted like this:

LOG:  checkpoint complete: ... write=0.044 s, sync=0.071 s, ...

I'm not sure if it applies for DETAIL, but at least it's what the
example at the error style guide[1] suggests:

Detail:     Failed syscall was shmget(key=%d, size=%u, 0%o).

Thanks!

Best, Jim


1 - https://www.postgresql.org/docs/current/error-style-guide.html

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.