From: Ronan Dunklau <ronan.dunklau@aiven.io>
To: pgsql-hackers@lists.postgresql.org, Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Subject: Re: Proposal: More structured logging
Date: Thu, 09 Sep 2021 11:15:36 +0200
Message-ID: <19106440.dsh0iPAc3d@aivenronan> (raw)
In-Reply-To: <03fa81f6-77b0-e7eb-b390-dfe04f180495@enterprisedb.com>
References: <3207907.AWbSqkKDnR@aivenronan>
<163276811.1OrvvjSa7g@aivenronan>
<03fa81f6-77b0-e7eb-b390-dfe04f180495@enterprisedb.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: ronan.dunklau@aiven.io, peter.eisentraut@enterprisedb.com
Subject: Re: Proposal: More structured logging
In-Reply-To: <19106440.dsh0iPAc3d@aivenronan>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox