MIME-Version: 1.0
References: <ba76c6bc-f03f-4285-bf16-47759cfcab9e@eisentraut.org> <20231205174034.GA2757816@nathanxps13>
In-Reply-To: <20231205174034.GA2757816@nathanxps13>
From: Robert Haas <robertmhaas@gmail.com>
Date: Tue, 5 Dec 2023 13:16:22 -0500
Message-ID: <CA+Tgmoas4qK-Um-RwSLAUXfKN+UothbofQ_3pfDtWGdrtaBNtA@mail.gmail.com>
Subject: Re: backtrace_on_internal_error
To: Nathan Bossart <nathandbossart@gmail.com>
Cc: Peter Eisentraut <peter@eisentraut.org>, pgsql-hackers <pgsql-hackers@postgresql.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://www.postgresql.org/message-id/CA%2BTgmoas4qK-Um-RwSLAUXfKN%2BUothbofQ_3pfDtWGdrtaBNtA%40mail.gmail.com>
Precedence: bulk

On Tue, Dec 5, 2023 at 12:40=E2=80=AFPM Nathan Bossart <nathandbossart@gmai=
l.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().

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