Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Mention jsonlog in description of logging_collector in GUC table
authorMichael Paquier <michael@paquier.xyz>
Sun, 2 Feb 2025 02:31:32 +0000 (11:31 +0900)
committerMichael Paquier <michael@paquier.xyz>
Sun, 2 Feb 2025 02:31:32 +0000 (11:31 +0900)
logging_collector was only mentioning stderr and csvlog, and forgot
about jsonlog.  Oversight in dc686681e079, that has added support for
jsonlog in log_destination.

While on it, the description in the GUC table is tweaked to be more
consistent with the documentation and postgresql.conf.sample.

Author: Umar Hayat
Reviewed-by: Ashutosh Bapat, Tom Lane
Discussion: https://postgr.es/m/CAD68Dp1K_vBYqBEukHw=1jF7e76t8aszGZTFL2ugi=H7r=a7MA@mail.gmail.com
Backpatch-through: 13

src/backend/utils/misc/guc.c

index 405623fd527011bd39cb4775066adb26216e1503..c8a837245ff1684497ff2860d0c4ef42b6662243 100644 (file)
@@ -1766,7 +1766,7 @@ static struct config_bool ConfigureNamesBool[] =
    },
    {
        {"logging_collector", PGC_POSTMASTER, LOGGING_WHERE,
-           gettext_noop("Start a subprocess to capture stderr output and/or csvlogs into log files."),
+           gettext_noop("Start a subprocess to capture stderr, csvlog and/or jsonlog into log files."),
            NULL
        },
        &Logging_collector,