Re: backtrace_on_internal_error - Mailing list pgsql-hackers

From Nathan Bossart
Subject Re: backtrace_on_internal_error
Date
Msg-id 20231205182845.GD2757816@nathanxps13
Whole thread Raw
In response to Re: backtrace_on_internal_error  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: backtrace_on_internal_error
List pgsql-hackers
On Tue, Dec 05, 2023 at 01:16:22PM -0500, Robert Haas wrote:
> 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().

Perhaps this should be a GUC that defaults to LOG or ERROR.

-- 
Nathan Bossart
Amazon Web Services: https://aws.amazon.com



pgsql-hackers by date:

Previous
From: Nathan Bossart
Date:
Subject: Re: Make COPY format extendable: Extract COPY TO format implementations
Next
From: Robert Haas
Date:
Subject: Re: backtrace_on_internal_error