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

From Andres Freund
Subject Re: A modest proposal: let's add PID to assertion failure messages
Date
Msg-id 20201006182748.ktk4se2gi4b3ggoy@alap3.anarazel.de
Whole thread Raw
In response to Re: A modest proposal: let's add PID to assertion failure messages  (Thomas Munro <thomas.munro@gmail.com>)
List pgsql-hackers
On 2020-10-05 10:20:01 +1300, Thomas Munro wrote:
> 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

+1



pgsql-hackers by date:

Previous
From: Anastasia Lubennikova
Date:
Subject: Re: [PATCH] Automatic HASH and LIST partition creation
Next
From: Andres Freund
Date:
Subject: Re: Add primary keys to system catalogs