Re: Printing backtrace of postgres processes

From: Justin Pryzby <pryzby(at)telsasoft(dot)com>
To: Greg Stark <stark(at)mit(dot)edu>
Cc: vignesh C <vignesh21(at)gmail(dot)com>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, torikoshia <torikoshia(at)oss(dot)nttdata(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Printing backtrace of postgres processes
Date: 2022-03-30 16:03:08
Message-ID: 20220330160308.GH28503@telsasoft.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Mar 30, 2022 at 11:53:52AM -0400, Greg Stark wrote:
> Sadly the cfbot is showing a patch conflict again. It's just a trivial
> conflict in the regression test schedule so I'm not going to update
> the status but it would be good to rebase it so we continue to get
> cfbot testing.

Done. No changes.

Attachment Content-Type Size
0001-Add-function-to-log-the-backtrace-of-the-specified-p.patch text/x-diff 31.1 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jelte Fennema 2022-03-30 16:08:16 Re: Add non-blocking version of PQcancel
Previous Message Jacob Champion 2022-03-30 16:02:09 Re: [PATCH] Expose port->authn_id to extensions and triggers