From 66a669efb0d65a9016d90aa49d7329d709b3776a Mon Sep 17 00:00:00 2001
From: Laurenz Albe <laurenz.albe@cybertec.at>
Date: Fri, 25 Sep 2026 17:04:38 +0200
Subject: [PATCH v1] Doc: no log_line_prefix in csvlog or jsonlog
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

The documentation didn't make clear that "log_line_prefix" is
not output if "log_destination" is "csvlog" or "jsonlog".

Author: Laurenz Albe <laurenz.albe@cybertec.at>
Reported-by: Michael Schönitzer <michael@schoenitzer.de>
Discussion: https://postgr.es/m/179032875673.1026201.6950455317699774504@wrigleys.postgresql.org
---
 doc/src/sgml/config.sgml | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index 0165eb9ec02..f277d311232 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -8224,7 +8224,8 @@ local0.*    /var/log/postgresql
       <listitem>
        <para>
          This is a <function>printf</function>-style string that is output at the
-         beginning of each log line.
+         beginning of each log line, except when <varname>log_destination</varname>
+         is <literal>csvlog</literal> or <literal>jsonlog</literal>.
          <literal>%</literal> characters begin <quote>escape sequences</quote>
          that are replaced with status information as outlined below.
          Unrecognized escapes are ignored. Other
-- 
2.55.0