public inbox for [email protected]  

help / color / mirror / Atom feed

From: Nathan Bossart <[email protected]>
To: Robert Haas <[email protected]>
Cc: Peter Eisentraut <[email protected]>
Cc: pgsql-hackers <[email protected]>
Subject: Re: backtrace_on_internal_error
Date: Tue, 5 Dec 2023 12:28:45 -0600
Message-ID: <20231205182845.GD2757816@nathanxps13> (raw)
In-Reply-To: <CA+Tgmoas4qK-Um-RwSLAUXfKN+UothbofQ_3pfDtWGdrtaBNtA@mail.gmail.com>
References: <[email protected]>
	<20231205174034.GA2757816@nathanxps13>
	<CA+Tgmoas4qK-Um-RwSLAUXfKN+UothbofQ_3pfDtWGdrtaBNtA@mail.gmail.com>

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

view thread (6+ messages)  latest in thread

reply

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: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: backtrace_on_internal_error
  In-Reply-To: <20231205182845.GD2757816@nathanxps13>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox