Re: errbacktrace - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: errbacktrace
Date
Msg-id CAFj8pRDkS_Ym-XAAgyibfZEraVde_Zn1wpuEw5NUkvqM1fna8g@mail.gmail.com
Whole thread Raw
In response to Re: errbacktrace  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers


po 12. 8. 2019 v 19:06 odesílatel Peter Eisentraut <peter.eisentraut@2ndquadrant.com> napsal:
On 2019-08-12 13:19, Pavel Stehule wrote:
> If I understand well, backtrace is displayed only when edata->funcname
> is same like backtrace_function GUC. Isn't it too strong limit?
>
> For example, I want to see backtrace for all PANIC level errors on
> production, and I would not to limit the source function?

We can add additional ways to invoke this once we have the basic
functionality in.

ok

Pavel

--
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: errbacktrace
Next
From: Stephen Frost
Date:
Subject: Re: Add "password_protocol" connection parameter to libpq