| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | michael(at)schoenitzer(dot)de, pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: log_line_prefix and JSON log format |
| Date: | 2026-09-25 22:13:10 |
| Message-ID: | d21988802bb3f6ca7dc7951175b79dde248e434e.camel@cybertec.at |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Fri, 2026-09-25 at 11:36 -0400, Tom Lane wrote:
> Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)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".
No objection to your wording.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2026-09-25 22:21:38 | Re: log_line_prefix and JSON log format |
| Previous Message | Matemática A3K | 2026-09-25 18:48:57 | Re: [Minor] Duplicated word in "Creating a Database" tutorial |