From: Tom Lane <tgl@sss.pgh.pa.us>
To: Laurenz Albe <laurenz.albe@cybertec.at>
cc: michael@schoenitzer.de, pgsql-docs@lists.postgresql.org
Subject: Re: log_line_prefix and JSON log format
In-reply-to: <42af2f4ed8afe739f2e8f8add80100b2ba2d7808.camel@cybertec.at>
References: <179032875673.1026201.6950455317699774504@wrigleys.postgresql.org>
 <42af2f4ed8afe739f2e8f8add80100b2ba2d7808.camel@cybertec.at>
Comments: In-reply-to Laurenz Albe <laurenz.albe@cybertec.at>
	message dated "Fri, 25 Sep 2026 17:10:50 +0200"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1885249.1790350583.1@sss.pgh.pa.us>
Date: Fri, 25 Sep 2026 11:36:23 -0400
Message-ID: <1885250.1790350583@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1885250.1790350583%40sss.pgh.pa.us>
Precedence: bulk

Laurenz Albe <laurenz.albe@cybertec.at> writes:
> On Fri, 2026-09-25 at 09:32 +0000, PG Doc comments form wrote:
>> I noticed, that it not documented anywhere what log_line_prefix will do, if
>> log_destination = 'jsonlog' (Or CSV). From my tests it seems it is ignored
>> and does nothing. But we weren't sure and would be helpful to have this
>> documented.

> True; here is a patch.

This wording seems like it might add confusion rather than remove it,
because it's not allowing for the fact that log_destination can be
a list.  I'd be inclined to write something more along the lines of
"... string that is output at the beginning of each log line that is
sent to stderr, syslog, or eventlog".

			regards, tom lane