From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
---|---|
To: | Ronan Dunklau <ronan(dot)dunklau(at)aiven(dot)io>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Proposal: More structured logging |
Date: | 2021-09-08 09:51:31 |
Message-ID: | 03fa81f6-77b0-e7eb-b390-dfe04f180495@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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.
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2021-09-08 09:58:22 | Re: Gather performance analysis |
Previous Message | Peter Eisentraut | 2021-09-08 09:45:15 | Re: public schema default ACL |