Re: Printing backtrace of postgres processes

On Wed, Jan 26, 2022 at 11:07 AM Bharath Rupireddy
<bharath(dot)rupireddyforpostgres(at)gmail(dot)com> wrote:
>
> On Tue, Jan 25, 2022 at 12:00 PM vignesh C <vignesh21(at)gmail(dot)com> wrote:
> > Thanks for the comments, attached v17 patch has the fix for the same.
>
> Have a minor comment on v17:
>
> can we modify the elog(LOG, to new style ereport(LOG, ?
> + elog(LOG_SERVER_ONLY, "current backtrace:%s", errtrace.data);
>
> /*----------
> * New-style error reporting API: to be used in this way:
> * ereport(ERROR,
> * errcode(ERRCODE_UNDEFINED_CURSOR),
> * errmsg("portal \"%s\" not found", stmt->portalname),
> * ... other errxxx() fields as needed ...);
> *

Attached v18 patch has the changes for the same.

Regards,
Vignesh