Revert "Add GUC backtrace_on_internal_error"
authorPeter Eisentraut
Mon, 29 Apr 2024 08:49:42 +0000 (10:49 +0200)
committerPeter Eisentraut
Mon, 29 Apr 2024 08:49:42 +0000 (10:49 +0200)
commit592a2283721f7143999364ef487f2b4993f5161d
treef3f2fc827ee8e775430ef695c7cc635be632b3a8
parent5c9f35fc48ea99e59300a267e090e3eafd1b3b0e
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%40mail.gmail.com#764bcdbb73e162787e1ad984935e51e3
doc/src/sgml/config.sgml
src/backend/utils/error/elog.c
src/backend/utils/misc/guc_tables.c
src/include/utils/guc.h