Re: backtrace_on_internal_error - Mailing list pgsql-hackers

From Robert Haas
Subject Re: backtrace_on_internal_error
Date
Msg-id CA+Tgmoas4qK-Um-RwSLAUXfKN+UothbofQ_3pfDtWGdrtaBNtA@mail.gmail.com
Whole thread Raw
In response to Re: backtrace_on_internal_error  (Nathan Bossart <nathandbossart@gmail.com>)
Responses Re: backtrace_on_internal_error
List pgsql-hackers
On Tue, Dec 5, 2023 at 12:40 PM Nathan Bossart <nathandbossart@gmail.com> wrote:
> On Tue, Dec 05, 2023 at 11:55:05AM +0100, Peter Eisentraut wrote:
> > Would others find this useful?
>
> Yes.  I think I would use this pretty frequently.

I think we should consider unconditionally emitting a backtrace when
an elog() is hit, instead of requiring a GUC. Or at least any elog()
that's not at a DEBUGn level. If the extra output annoys anybody, that
means they're regularly hitting an elog(), and it ought to be promoted
to ereport().

--
Robert Haas
EDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: trying again to get incremental backup
Next
From: Nathan Bossart
Date:
Subject: Re: Make COPY format extendable: Extract COPY TO format implementations