Message-ID: <d21988802bb3f6ca7dc7951175b79dde248e434e.camel@cybertec.at>
Subject: Re: log_line_prefix and JSON log format
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: michael@schoenitzer.de, pgsql-docs@lists.postgresql.org
Date: Sat, 26 Sep 2026 00:13:10 +0200
In-Reply-To: <1885250.1790350583@sss.pgh.pa.us>
References: <179032875673.1026201.6950455317699774504@wrigleys.postgresql.org>
	 <42af2f4ed8afe739f2e8f8add80100b2ba2d7808.camel@cybertec.at>
	 <1885250.1790350583@sss.pgh.pa.us>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.60.2 (3.60.2-2.fc44) 
MIME-Version: 1.0
Archived-At: 
 <https://www.postgresql.org/message-id/d21988802bb3f6ca7dc7951175b79dde248e434e.camel%40cybertec.at>
Precedence: bulk

On Fri, 2026-09-25 at 11:36 -0400, Tom Lane wrote:
> 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 =3D '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 th=
is
> > > documented.
>=20
> > True; here is a patch.
>=20
> 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.=C2=A0 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".

No objection to your wording.

Yours,
Laurenz Albe