Re: Printing backtrace of postgres processes

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: vignesh C <vignesh21(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Printing backtrace of postgres processes
Date: 2021-01-15 08:53:05
Message-ID: 55526d79-247d-83a1-0961-7d42e0db1870@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2021-01-15 08:59:02 Re: Occasional tablespace.sql failures in check-world -jnn
Previous Message Julien Rouhaud 2021-01-15 08:47:41 Re: list of extended statistics on psql