aboutsummaryrefslogtreecommitdiff
path: root/src/backend/utils/misc/guc_tables.c
diff options
context:
space:
mode:
authorMichael Paquier <michael@paquier.xyz>2023-12-11 11:49:02 +0100
committerMichael Paquier <michael@paquier.xyz>2023-12-11 11:49:02 +0100
commitc7a3e6b46d38f880f42642df003796b9bf99c1a8 (patch)
treec6e419196dce96b6e4709d55e312588c6406a61a /src/backend/utils/misc/guc_tables.c
parent8d7d2197f31c1839db4726d1a12cb29016f4fa36 (diff)
downloadpostgresql-c7a3e6b46d38f880f42642df003796b9bf99c1a8.tar.gz
postgresql-c7a3e6b46d38f880f42642df003796b9bf99c1a8.zip
Remove trace_recovery_messages
This GUC was intended as a debugging help in the 9.0 area when hot standby and streaming replication were being developped, able to offer more information at LOG level rather than DEBUGn. There are more tools available these days that are able to offer rather equivalent information, like pg_waldump introduced in 9.3. It is not obvious how this facility is useful these days, so let's remove it. Author: Bharath Rupireddy Discussion: https://postgr.es/m/ZXEXEAUVFrvpquSd@paquier.xyz
Diffstat (limited to 'src/backend/utils/misc/guc_tables.c')
-rw-r--r--src/backend/utils/misc/guc_tables.c18
1 files changed, 0 insertions, 18 deletions
diff --git a/src/backend/utils/misc/guc_tables.c b/src/backend/utils/misc/guc_tables.c
index 6474e35ec04..f7c9882f7c5 100644
--- a/src/backend/utils/misc/guc_tables.c
+++ b/src/backend/utils/misc/guc_tables.c
@@ -525,7 +525,6 @@ int log_parameter_max_length_on_error = 0;
int log_temp_files = -1;
double log_statement_sample_rate = 1.0;
double log_xact_sample_rate = 0;
-int trace_recovery_messages = LOG;
char *backtrace_functions;
int temp_file_limit = -1;
@@ -4781,23 +4780,6 @@ struct config_enum ConfigureNamesEnum[] =
},
{
- {"trace_recovery_messages", PGC_SIGHUP, DEVELOPER_OPTIONS,
- gettext_noop("Enables logging of recovery-related debugging information."),
- gettext_noop("Each level includes all the levels that follow it. The later"
- " the level, the fewer messages are sent."),
- GUC_NOT_IN_SAMPLE,
- },
- &trace_recovery_messages,
-
- /*
- * client_message_level_options allows too many values, really, but
- * it's not worth having a separate options array for this.
- */
- LOG, client_message_level_options,
- NULL, NULL, NULL
- },
-
- {
{"track_functions", PGC_SUSET, STATS_CUMULATIVE,
gettext_noop("Collects function-level statistics on database activity."),
NULL