pgsql: Revert "Add GUC backtrace_on_internal_error"

Started by Peter Eisentrautabout 2 years ago1 messagescomitters

peter_e@gmx.net

about 2 years ago

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: /messages/by-id/CAGECzQTChkvn5Xj772LB3=xo2x_LcaO5O0HQvXqobm1xVp6+4w@mail.gmail.com

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(-)