mirror of
https://github.com/postgres/postgres.git
synced 2025-06-25 01:02:05 +03:00
Revert "Add GUC backtrace_on_internal_error"
This reverts commit a740b213d4
.
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
This commit is contained in:
@ -531,7 +531,6 @@ int log_temp_files = -1;
|
||||
double log_statement_sample_rate = 1.0;
|
||||
double log_xact_sample_rate = 0;
|
||||
char *backtrace_functions;
|
||||
bool backtrace_on_internal_error = false;
|
||||
|
||||
int temp_file_limit = -1;
|
||||
|
||||
@ -770,16 +769,6 @@ StaticAssertDecl(lengthof(config_type_names) == (PGC_ENUM + 1),
|
||||
|
||||
struct config_bool ConfigureNamesBool[] =
|
||||
{
|
||||
{
|
||||
{"backtrace_on_internal_error", PGC_SUSET, DEVELOPER_OPTIONS,
|
||||
gettext_noop("Log backtrace for any error with error code XX000 (internal error)."),
|
||||
NULL,
|
||||
GUC_NOT_IN_SAMPLE
|
||||
},
|
||||
&backtrace_on_internal_error,
|
||||
false,
|
||||
NULL, NULL, NULL
|
||||
},
|
||||
{
|
||||
{"enable_seqscan", PGC_USERSET, QUERY_TUNING_METHOD,
|
||||
gettext_noop("Enables the planner's use of sequential-scan plans."),
|
||||
|
Reference in New Issue
Block a user