Re: errbacktrace

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: errbacktrace
Date: 2019-08-12 17:08:30
Message-ID: CAFj8pRDkS_Ym-XAAgyibfZEraVde_Zn1wpuEw5NUkvqM1fna8g@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

po 12. 8. 2019 v 19:06 odesílatel Peter Eisentraut <
peter(dot)eisentraut(at)2ndquadrant(dot)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
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2019-08-12 17:14:15 Re: Add "password_protocol" connection parameter to libpq
Previous Message Peter Eisentraut 2019-08-12 17:06:29 Re: errbacktrace