Re: Add errdetail() with PID and UID about source of termination signal
Andrew Dunstan <andrew@dunslane.net>
From: Andrew Dunstan <andrew@dunslane.net>
To: Kirill Reshke <reshkekirill@gmail.com>, Chao Li <li.evan.chao@gmail.com>
Cc: 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:14:52Z
Lists: pgsql-hackers
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
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Only show signal-sender PID/UID detail in server log
- b772f3fcad18 19 (unreleased) landed
-
Make psql DETAIL line test unconditionally optional.
- 446c400fd89b 19 (unreleased) landed
-
Rework signal handler infrastructure to pass sender info as argument.
- 3e2a1496bae6 19 (unreleased) landed
-
Add errdetail() with PID and UID about source of termination signal.
- 55890a919454 19 (unreleased) landed