Re: A modest proposal: let's add PID to assertion failure messages - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: A modest proposal: let's add PID to assertion failure messages
Date
Msg-id CA+hUKGJ9V9fYba5oYiPn2QdO4uQUxUcTesMLLHHK4YJ=Gt04Mg@mail.gmail.com
Whole thread Raw
In response to A modest proposal: let's add PID to assertion failure messages  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: A modest proposal: let's add PID to assertion failure messages  (Michael Paquier <michael@paquier.xyz>)
Re: A modest proposal: let's add PID to assertion failure messages  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On Mon, Oct 5, 2020 at 10:08 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> In these days when we run almost all test cases in parallel, it's
> frequently not that easy to tie a "TRAP: ..." message in the log
> to nearby log messages.  (The postmaster's subsequent complaint
> often helps, but it could be some distance away in the log; and
> good luck untangling things if more than one Assert failure happens
> concurrently.)  We could add a simple bread crumb trail by
> including the process's PID in such messages.  Any objections?

+1



pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: Buglets in equivclass.c
Next
From: Tomas Vondra
Date:
Subject: Re: [HACKERS] Custom compression methods