From 5f5f519030a6f58af1e7791650eaaf188c6719cd Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fabr=C3=ADzio=20de=20Royes=20Mello?= Date: Tue, 17 Oct 2023 15:33:31 -0300 Subject: [PATCH] PG16: Fix ts_bgw_log_level bootval When defining a GUC Postgres do a cross-check between the initial value of the C declaration associated to a GUC and its actual boot value in assert-enabled builds. Previous PR #6206 didn't fixed it entirely and this happen just on PG16. postgres/postgres@a73952b7 --- src/guc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/guc.c b/src/guc.c index 95443f277a0..1485e2c7d3c 100644 --- a/src/guc.c +++ b/src/guc.c @@ -727,7 +727,7 @@ _guc_init(void) "Log level for the scheduler and workers of the background worker " "subsystem. Requires configuration reload to change.", /* valueAddr= */ &ts_guc_bgw_log_level, - /* bootValue= */ log_min_messages, + /* bootValue= */ WARNING, /* options= */ loglevel_options, /* context= */ PGC_SIGHUP, 0,