| From: | Matemática A3K <matematica(dot)a3k(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, 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 16:14:12 |
| Message-ID: | CA+FDnhLoTuqkgRzffP3ajN82nQc-mFvc7iS=4u22eJzaugZxaw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Fri, Sep 25, 2026 at 12:36 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> 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".
>
> regards, tom lane
>
I agree with Tom
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matemática A3K | 2026-09-25 16:17:52 | Re: [Minor] Improve reading in "2. A Brief History of PostgreSQL" |
| Previous Message | Tom Lane | 2026-09-25 15:36:23 | Re: log_line_prefix and JSON log format |