Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xA5h1-00000002RhW-3a8c for pgsql-docs@arkaria.postgresql.org; Fri, 25 Sep 2026 13:10:24 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.98.2) (envelope-from ) id 1xA5gz-00000000mkm-1ezj for pgsql-docs@arkaria.postgresql.org; Fri, 25 Sep 2026 13:10:21 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xA2Iq-000000009jM-1CYr for pgsql-docs@lists.postgresql.org; Fri, 25 Sep 2026 09:33:12 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xA2Ik-00000001DDi-3ne9 for pgsql-docs@lists.postgresql.org; Fri, 25 Sep 2026 09:33:11 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Message-ID:Date:Reply-To:Cc:From:To:Subject: Content-Transfer-Encoding:MIME-Version:Content-Type:Sender:Content-ID: Content-Description:In-Reply-To:References; bh=UH3q4yy17FNnmyCaPj4xqlwQjZNP1P+qBmNhcbinncc=; b=6R1qSepYNKt/rCRBZS78qXCJZy pwEpGTKj6IWqxWyf3DCwXnt3zVjVICLnDAbAEVZ73UhP8NS/imDAXZ+w39HbvfiXbNYtzfaPn9HRc 3rOmJx5YtWFIHq7XqU7Q3xMyeE3/LzSBvsKiI+bZRx95KnIQw/3ZfXlBxX7pRAZEjdLW6U8t8F148 aSUcbzGYMXh4fwEqsNKtbqOLM7UvCG8KSHX/E8k2f3XFatyN9YDpGl/KHmIDVjnNBsj4/8HXW3Es7 S7XNk6g8GoiQ1MFZvFa92vawfpDPXn81sjZAxpt1NoRONsH9EVGk7xkZ0zdCM3A2qVdRQuXBMPPF9 H2YDFihg==; Received: from wrigleys.postgresql.org ([2a02:16a8:dc51::60]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1xA2Ij-003TjG-1B for pgsql-docs@lists.postgresql.org; Fri, 25 Sep 2026 09:33:05 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.98.2) (envelope-from ) id 1xA2Ih-00000009zHY-158r for pgsql-docs@lists.postgresql.org; Fri, 25 Sep 2026 09:33:03 +0000 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Subject: log_line_prefix and JSON log format To: pgsql-docs@lists.postgresql.org From: PG Doc comments form Cc: michael@schoenitzer.de Reply-To: michael@schoenitzer.de, pgsql-docs@lists.postgresql.org Date: Fri, 25 Sep 2026 09:32:36 +0000 Message-ID: <179032875673.1026201.6950455317699774504@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/18/index.html Description: 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 this documented.