Re: Printing backtrace of postgres processes

From: vignesh C <vignesh21(at)gmail(dot)com>
To: Justin Pryzby <pryzby(at)telsasoft(dot)com>
Cc: 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-12 07:29:08
Message-ID: CALDaNm0Wz0M----FPjRmPk3ifhffD-MxpajZX5EVYN=1gOFCQw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Mar 9, 2022 at 9:26 PM Justin Pryzby <pryzby(at)telsasoft(dot)com> wrote:
>
> rebased to appease cfbot.
>
> + couple of little fixes as 0002.

Thanks for rebasing and fixing a few issues. I have taken all your
changes except for mcxtfuncs changes as those changes were not done as
part of this patch. Attached v19 patch which has the changes for the
same.

Regards,
Vignesh

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message vignesh C 2022-03-12 07:59:06 Re: Logical replication - schema change not invalidating the relation cache
Previous Message Imseih (AWS), Sami 2022-03-12 07:00:06 Re: Add index scan progress to pg_stat_progress_vacuum