Re: errbacktrace - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: errbacktrace
Date
Msg-id d4e057c3-860e-9f62-3d25-442369ae784b@2ndquadrant.com
Whole thread Raw
In response to Re: errbacktrace  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: errbacktrace  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
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.

-- 
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: Add "password_protocol" connection parameter to libpq
Next
From: Pavel Stehule
Date:
Subject: Re: errbacktrace