Re: Printing backtrace of postgres processes

From: Greg Stark <stark(at)mit(dot)edu>
To: vignesh C <vignesh21(at)gmail(dot)com>
Cc: Justin Pryzby <pryzby(at)telsasoft(dot)com>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, torikoshia <torikoshia(at)oss(dot)nttdata(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Printing backtrace of postgres processes
Date: 2022-03-30 15:53:52
Message-ID: CAM-w4HMw2yCZceg+iwm+N5QFZ4s+tS4ra7AxaNfzS1UP+CZOYg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jacob Champion 2022-03-30 16:02:09 Re: [PATCH] Expose port->authn_id to extensions and triggers
Previous Message Greg Stark 2022-03-30 15:51:53 Re: Frontend error logging style