From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Pavel Stehule <pavel.stehule@gmail.com>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Dmitry Dolgov <9erthalion6@gmail.com>
Cc: Thomas Munro <thomas.munro@gmail.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: errbacktrace
Date: Mon, 12 Aug 2019 19:06:29 +0200
Message-ID: <d4e057c3-860e-9f62-3d25-442369ae784b@2ndquadrant.com> (raw)
In-Reply-To: <CAFj8pRDG3tCD5k+r2D5Y++fc7aR3LQUQF-3EA6XJhkGtJgXyzA@mail.gmail.com>
References: <CA+q6zcViaQ-Lpgd3ELnZ-+UqDEL4SqWWLLCARHPSyd5nYageuQ@mail.gmail.com>
<20190708162851.GA11054@alvherre.pgsql>
<CAFj8pRDG3tCD5k+r2D5Y++fc7aR3LQUQF-3EA6XJhkGtJgXyzA@mail.gmail.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: peter.eisentraut@2ndquadrant.com, pavel.stehule@gmail.com, alvherre@2ndquadrant.com, 9erthalion6@gmail.com, thomas.munro@gmail.com
Subject: Re: errbacktrace
In-Reply-To: <d4e057c3-860e-9f62-3d25-442369ae784b@2ndquadrant.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox