Re: backtrace_on_internal_error - Mailing list pgsql-hackers

From Robert Haas
Subject Re: backtrace_on_internal_error
Date
Msg-id CA+TgmoZROvY+URoUHwwO+wvdx-VdiGbqozh4+D0QuxWDE2uEHg@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 1:28 PM Nathan Bossart <nathandbossart@gmail.com> wrote:
> 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.

Why?

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



pgsql-hackers by date:

Previous
From: Nathan Bossart
Date:
Subject: Re: backtrace_on_internal_error
Next
From: "Tristan Partin"
Date:
Subject: Re: psql not responding to SIGINT upon db reconnection