From: Peter Eisentraut <peter@eisentraut.org>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Revert "Add GUC backtrace_on_internal_error"
Date: Mon, 29 Apr 2024 09:11:24 +0000
Message-ID: <E1s1N2h-000bE6-L9@gemulon.postgresql.org> (raw)
Revert "Add GUC backtrace_on_internal_error"
This reverts commit a740b213d4b4d3360ad0cac696e47e5ec0eb8864.
Subsequent discussion showed that there was interest in a more general
facility to configure when server log events would produce backtraces,
and this existing limited way couldn't be extended in a compatible
way. So the consensus was to revert this for PostgreSQL 17 and
reconsider this topic for PostgreSQL 18.
Discussion: https://www.postgresql.org/message-id/flat/CAGECzQTChkvn5Xj772LB3%3Dxo2x_LcaO5O0HQvXqobm1xVp6%2B4w%4...
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/592a2283721f7143999364ef487f2b4993f5161d
Modified Files
--------------
doc/src/sgml/config.sgml | 27 ---------------------------
src/backend/utils/error/elog.c | 8 +++-----
src/backend/utils/misc/guc_tables.c | 11 -----------
src/include/utils/guc.h | 1 -
4 files changed, 3 insertions(+), 44 deletions(-)
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: pgsql-committers@postgresql.org
Cc: peter@eisentraut.org, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Revert "Add GUC backtrace_on_internal_error"
In-Reply-To: <E1s1N2h-000bE6-L9@gemulon.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox