Postgres Pro
Downloads
Home   >   mailing lists

Re: Printing backtrace of postgres processes - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Printing backtrace of postgres processes
Date
Msg-id 20210115201011.noomcygirzge43ir@alap3.anarazel.de
Whole thread Raw
In response to Re: Printing backtrace of postgres processes  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
Responses Re: Printing backtrace of postgres processes  (vignesh C <vignesh21@gmail.com>)
List pgsql-hackers
Tree view 
On 2021-01-15 09:53:05 +0100, Peter Eisentraut wrote:
> On 2020-12-08 10:38, vignesh C wrote:
> > I have implemented printing of backtrace based on handling it in
> > CHECK_FOR_INTERRUPTS. This patch also includes the change to allow
> > getting backtrace of any particular process based on the suggestions.
> > Attached patch has the implementation for the same.
> > Thoughts?
> 
> Are we willing to use up a signal for this?

Why is a full signal needed? Seems the procsignal infrastructure should
suffice?

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: jit and explain nontext
Next
From: David Zhang
Date:
Subject: Re: Add table access method as an option to pgbench