| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | pgsql: Revert "Add GUC backtrace_on_internal_error" |
| Date: | 2024-04-29 09:11:24 |
| Message-ID: | E1s1N2h-000bE6-L9@gemulon.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
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.
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(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2024-04-29 09:27:02 | pgsql: libpq: If ALPN is not used, make PQsslAttribute(conn, "alpn") == |
| Previous Message | Heikki Linnakangas | 2024-04-28 19:59:05 | pgsql: Fix documentation and comments on what happens after GSS rejecti |