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

Kirill Reshke <reshkekirill@gmail.com>

From: Kirill Reshke <reshkekirill@gmail.com>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: Chao Li <li.evan.chao@gmail.com>, Jakub Wartak <jakub.wartak@enterprisedb.com>, Andres Freund <andres@anarazel.de>, Jim Jones <jim.jones@uni-muenster.de>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2026-04-15T12:45:01Z
Lists: pgsql-hackers
On Wed, 15 Apr 2026 at 17:14, Andrew Dunstan <andrew@dunslane.net> wrote:
>
>
> On 2026-04-15 We 7:45 AM, Kirill Reshke wrote:
> > I am seeing 3e2a1496bae628c379ca0a11ef5f5ba666f24ae8 merged into
> > master today, and I am a bit surprised.
> >
> > This is a feature for my taste and the feature freeze was on 8th April
> > 12 UTC. Am I wrong?
> >
>
>
> It's a fix for a feature that was committed before feature freeze.
>
>
> cheers
>
>
> andrew
>
> --
> Andrew Dunstan
> EDB: https://www.enterprisedb.com


Ok, sorry


-- 
Best regards,
Kirill Reshke



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.