Re: Proposal: More structured logging - Mailing list pgsql-hackers

From Ronan Dunklau
Subject Re: Proposal: More structured logging
Date
Msg-id 19106440.dsh0iPAc3d@aivenronan
Whole thread Raw
In response to Re: Proposal: More structured logging  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
List pgsql-hackers
Le mercredi 8 septembre 2021, 11:51:31 CEST Peter Eisentraut a écrit :
> On 01.09.21 10:00, Ronan Dunklau wrote:
> > In-core it would open up the possibility to split log messages into
> > different fields, for example the different statistics reported in the
> > logs by VACUUM / ANALYZE VERBOSE and make it easier to consume the output
> > without having to parse the message. Parsing the message also means that
> > any tool parsing it needs to either be aware of the locale, or to force
> > the user to use a specific one.
>
> I think those messages would themselves have substructure.  For example,
> the current message
>
>      "I/O timings: read: %.3f ms, write: %.3f ms\n"
>
> might be
>
>      {"I/O timings": {"read": ..., "write": ...}}
>
> and that in turn is already part of a larger message.
>
> So just having a single level of tags wouldn't really work for this.

I agree having a nested structure may feel more natural, but I don't think it
would matter too much if we standardize on ini-style property names (ie,
iotimings.read, iotimings.write and so on...)

Regards,

--
Ronan Dunklau





pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: row filtering for logical replication
Next
From: "蔡梦娟(玊于)"
Date:
Subject: 回复:Queries that should be canceled will get stuck on secure_write function